From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: virtio-comment@lists.oasis-open.org
Cc: anton.yakovlev@opensynergy.com
Subject: [virtio-comment] Re: [RFC PATCH] virtio-snd: improve PCM command lifecycle description
Date: Tue, 7 Nov 2023 11:44:18 +0100 [thread overview]
Message-ID: <CAHYGQ0wzMjCcWGJSSQiyc52eR3JKpBWOHgQ17Uv0Ffigf2kCkQ@mail.gmail.com> (raw)
In-Reply-To: <e577462c42778eba4f3fc96cc08038fd6a2b4390.1689090186.git.mvaralar@redhat.com>
Ping Anton.
Matias
On Wed, Jul 12, 2023 at 10:37 AM Matias Ezequiel Vara Larsen
<mvaralar@redhat.com> wrote:
>
> The PCM command lifecycle can be described as a state-machine in which
> the switching between states is triggered by commands. This commit
> explicitly presents the different states and the commands that are
> allowed in a given state. This commit leaves to the implementation the
> decision the state reached depending on the command.
>
> Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> ---
> device-types/sound/description.tex | 26 +++++++++++++++++++-------
> 1 file changed, 19 insertions(+), 7 deletions(-)
>
> diff --git a/device-types/sound/description.tex b/device-types/sound/description.tex
> index 54c9c8e..55e93af 100644
> --- a/device-types/sound/description.tex
> +++ b/device-types/sound/description.tex
> @@ -397,9 +397,21 @@ \subsubsection{PCM Control Messages}\label{sec:Device Types / Sound Device / Dev
> \item[\field{stream_id}] specifies a PCM stream identifier from 0 to \field{streams} - 1.
> \end{description}
>
> -\paragraph{PCM Command Lifecycle}
> +\paragraph{PCM Command Lifecycle State Machine}
>
> -A PCM stream has the following command lifecycle:
> +A PCM stream can be represented by a state-machine made up of the following
> +states:
> +\begin{description}
> +\item SET PARAMETERS
> +\item PREPARE
> +\item START
> +\item STOP
> +\item RELEASE
> +\end{description}
> +
> +A command triggers the transition between these states. To what state to switch
> +depends on the implementation. Depending on the state, only certain commands
> +are valid. An error may occur if an invalid command is triggered.
>
> \begin{enumerate}
> \item SET PARAMETERS
> @@ -407,13 +419,13 @@ \subsubsection{PCM Control Messages}\label{sec:Device Types / Sound Device / Dev
> The driver negotiates the stream parameters (format, transport, etc) with
> the device.
>
> -Possible valid transitions: set parameters, prepare.
> +Possible valid commands: set parameters, prepare.
>
> \item PREPARE
>
> The device prepares the stream (allocates resources, etc).
>
> -Possible valid transitions: set parameters, prepare, start, release.
> +Possible valid commands: set parameters, prepare, start, release.
>
> \item Output only: the driver transfers data for pre-buffing.
>
> @@ -421,7 +433,7 @@ \subsubsection{PCM Control Messages}\label{sec:Device Types / Sound Device / Dev
>
> The device starts the stream (unmute, putting into running state, etc).
>
> -Possible valid transitions: stop.
> +Possible valid commands: stop.
>
> \item The driver transfers data to/from the stream.
>
> @@ -429,13 +441,13 @@ \subsubsection{PCM Control Messages}\label{sec:Device Types / Sound Device / Dev
>
> The device stops the stream (mute, putting into non-running state, etc).
>
> -Possible valid transitions: start, release.
> +Possible valid commands: start, release.
>
> \item RELEASE
>
> The device releases the stream (frees resources, etc).
>
> -Possible valid transitions: set parameters, prepare.
> +Possible valid commands: set parameters, prepare.
>
> \end{enumerate}
>
> --
> 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/
prev parent reply other threads:[~2023-11-07 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:37 [virtio-comment] [RFC PATCH] virtio-snd: improve PCM command lifecycle description Matias Ezequiel Vara Larsen
2023-11-07 10:44 ` Matias Ezequiel Vara Larsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHYGQ0wzMjCcWGJSSQiyc52eR3JKpBWOHgQ17Uv0Ffigf2kCkQ@mail.gmail.com \
--to=mvaralar@redhat.com \
--cc=anton.yakovlev@opensynergy.com \
--cc=virtio-comment@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).