Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anton Yakovlev <anton.yakovlev@opensynergy.com>,
	virtio-comment@lists.oasis-open.org,
	liam.r.girdwood@linux.intel.com, tiwai@suse.de,
	broonie@kernel.org, maz@kernel.org, james.morse@arm.com,
	julien.thierry.kdev@gmail.com, suzuki.poulose@arm.com,
	cdupontd@redhat.com, kraxel@redhat.com, jean-philippe@linaro.org
Subject: Re: [virtio-comment] [PATCH] virtio-snd: add support for audio controls
Date: Mon, 20 Jun 2022 15:47:01 +0200	[thread overview]
Message-ID: <87mte7qwfe.fsf@redhat.com> (raw)
In-Reply-To: <20220617071406-mutt-send-email-mst@kernel.org>

On Fri, Jun 17 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Tue, Jul 27, 2021 at 05:57:23PM +0200, Cornelia Huck wrote:
>> On Tue, Apr 20 2021, Anton Yakovlev <anton.yakovlev@opensynergy.com> wrote:
>> 
>> > This patch extends the virtio sound device specification by adding
>> > support for audio controls. Audio controls can be used to set the volume
>> > level, mute/unmute the audio signal, switch different modes/states of
>> > the virtual sound device, etc.
>> >
>> > Signed-off-by: Anton Yakovlev <anton.yakovlev@opensynergy.com>
>> > ---
>> >  conformance.tex  |   5 +
>> >  virtio-sound.tex | 374 ++++++++++++++++++++++++++++++++++++++++++++++-
>> >  2 files changed, 378 insertions(+), 1 deletion(-)
>> >
>> 
>> > @@ -50,6 +53,7 @@ \subsection{Device Configuration Layout}\label{sec:Device Types / Sound Device /
>> >      le32 jacks;
>> >      le32 streams;
>> >      le32 chmaps;
>> > +    le32 controls;
>> >  };
>> >  \end{lstlisting}
>> >  
>> > @@ -62,6 +66,9 @@ \subsection{Device Configuration Layout}\label{sec:Device Types / Sound Device /
>> >  PCM streams.
>> >  \item[\field{chmaps}] (driver-read-only) indicates a total number of all available
>> >  channel maps.
>> > +\item[\field{controls}] (driver-read-only) indicates a total number of all available
>> > +control elements if VIRTIO_SND_F_CTLS has been negotiated.
>> 
>> While the driver is not supposed to read this if the feature has not
>> been negotiated, do we also want to add a normative statement about what
>> the device is supposed to do in this case? Does the field always exist?
>
>
> Cornelia this is a general issue in the spec. We should be clearer
> that
> - drivers should be ready for config space to be shorter
> or longer than described here, as long as they do not
> need to access outside of it, it is ok.
> - negotiated/offered confusion

Yes, I remember we had some discussions about that in the meantime...

>
>
> I will revive my proposal where feature is negotiated even before
> FEATURES_OK
>
> I think this can stand as is for now.

Fine with me.


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/


      reply	other threads:[~2022-06-20 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 18:32 [virtio-comment] [PATCH] virtio-snd: add support for audio controls Anton Yakovlev
2021-05-18 14:20 ` [virtio-comment] " Anton Yakovlev
2021-07-27 15:57 ` [virtio-comment] " Cornelia Huck
2022-06-17 11:20   ` Michael S. Tsirkin
2022-06-20 13:47     ` Cornelia Huck [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=87mte7qwfe.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=anton.yakovlev@opensynergy.com \
    --cc=broonie@kernel.org \
    --cc=cdupontd@redhat.com \
    --cc=james.morse@arm.com \
    --cc=jean-philippe@linaro.org \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=maz@kernel.org \
    --cc=mst@redhat.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tiwai@suse.de \
    --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