virtio-sound: add latency_bytes definition
PATCH 1/1 virtio-sound: add latency_bytes definition
This commit aims at providing a better definition of latency_bytes. To do so, this commit defines latency_bytes as is defined in Crosvm.
---
Changelog:
v0 -> v1:
* specify that the delay is due to the device implementation.
--- device-types/sound/description.tex | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
device-types/sound/description.tex +4 -1
@@ -694,7 +694,10 @@ \subsubsection{PCM I/O Messages}\label{sec:Device Types / Sound Device / Device \begin{description} \item[\field{status}] contains VIRTIO_SND_S_OK if an operation is successful, and VIRTIO_SND_S_IO_ERR otherwise. -\item[\field{latency_bytes}] indicates the current device latency. +\item[\field{latency_bytes}] indicates the current additional delay caused by +the device's implementation. For playback, this is the amount of bytes that +must be consumed before the current request can be played. For capture, this is +the latency in terms of bytes that the capture buffer was recorded. \end{description} Since all buffers in the queue (with one exception) should be of the size
Signature · 18 lines
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: [email protected] Unsubscribe: [email protected] List help: [email protected] 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/
Quoted 31 lines · Matias Ezequiel Vara Larsen
This commit aims at providing a better definition of
latency_bytes. To do so, this commit defineslatency_bytesas is defined in Crosvm.Signed-off-by Matias Ezequiel Vara Larsen <[email protected]>---
Changelog:
v0 -> v1:
* specify that the delay is due to the device implementation.--- device-types/sound/description.tex | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)device-types/sound/description.tex +4
-1@@ -694,7 +694,10 @@ \subsubsection{PCM I/O Messages}\label{sec:Device Types / Sound Device / Device \begin{description} \item[\field{status}] contains VIRTIO_SND_S_OK if an operation is successful, and VIRTIO_SND_S_IO_ERR otherwise. -\item[\field{latency_bytes}] indicates the current device latency. +\item[\field{latency_bytes}] indicates the current additional delay caused by +the device's implementation. For playback, this is the amount of bytes that +must be consumed before the current request can be played. For capture, this is +the latency in terms of bytes that the capture buffer was recorded. \end{description} Since all buffers in the queue (with one exception) should be of the sizeSignature · 1 line
2.41.0
Ping @Anton, thanks.
Matias
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/