* [virtio-comment] [PATCH] virtio-can: rephrase notification mechanism
@ 2024-02-28 16:16 Matias Ezequiel Vara Larsen
0 siblings, 0 replies; only message in thread
From: Matias Ezequiel Vara Larsen @ 2024-02-28 16:16 UTC (permalink / raw)
To: virtio-comment; +Cc: mvaralar, harald.mommer
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
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2024-02-28 16:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-28 16:16 [virtio-comment] [PATCH] virtio-can: rephrase notification mechanism Matias Ezequiel Vara Larsen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.