[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [PATCH] virtio-can: rephrase notification mechanism
This commit rephrases the notification mechanism. Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com> --- * This patch applies on top of virtio-1.4, which has not been released yet. --- device-types/can/description.tex | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/device-types/can/description.tex b/device-types/can/description.tex index 2511d9c..2931aa9 100644 --- a/device-types/can/description.tex +++ b/device-types/can/description.tex @@ -128,13 +128,12 @@ \subsubsection{Controller Mode}\label{sec:Device Types / CAN Device / Device Ope \end{lstlisting} If the transition succeeded the \field{result} is VIRTIO_CAN_RESULT_OK -otherwise it is VIRTIO_CAN_RESULT_NOT_OK. If a status update is -necessary, the device updates the configuration \field{status} before -marking the request used. As the configuration \field{status} change is -caused by a request from the driver the device is allowed to omit the -configuration change notification here. The device marks the request -used when the CAN controller has finalized the transition to the -requested controller mode. +otherwise it is VIRTIO_CAN_RESULT_NOT_OK. If a status update is necessary, the +device updates the configuration \field{status} before marking the request +used. The device may omit the configuration change notification as the +configuration \field{status} change is requested by the driver. The device +marks the request used when the CAN controller has finalized the transition to +the requested controller mode. On transition to the STOPPED state the device cancels all CAN messages already pending for transmission and marks them as used with base-commit: 37c6a406678a5ee891fdf5671298cb4fcfa517f2 -- 2.41.0
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]