From: Takashi Iwai <tiwai@suse.de>
To: Aiswarya Cyriac <aiswarya.cyriac@opensynergy.com>
Cc: mst@redhat.com, jasowang@redhat.com, perex@perex.cz,
tiwai@suse.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
virtualization@lists.linux-foundation.org,
virtio-dev@lists.oasis-open.org,
Anton Yakovlev <anton.yakovlev@opensynergy.com>
Subject: Re: [v2 PATCH 0/1] ALSA: virtio: add support for audio controls
Date: Fri, 09 Feb 2024 14:01:56 +0100 [thread overview]
Message-ID: <877cjd23ln.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240115133654.576068-1-aiswarya.cyriac@opensynergy.com>
On Mon, 15 Jan 2024 14:36:53 +0100,
Aiswarya Cyriac wrote:
>
> From: Anton Yakovlev <anton.yakovlev@opensynergy.com>
>
> Changes in v2
> - Fix reporting of incorrect number of items for ENUMERATED controls
>
> Implementation of support for audio controls in accordance with the
> extension of the virtio sound device specification[1] planned for
> virtio-v1.3-cs01.
>
> Design of virtual audio controls is based on and derived from ALSA
> audio controls. It allows the driver to perform all standard operations,
> such as reading and writing audio control value, as well as working with
> metadata (represented in the TLV form).
>
> The driver part was tested on top of the Linux 5.10 kernel.
>
> As a device part was used OpenSynergy proprietary implementation.
>
> [1] https://lists.oasis-open.org/archives/virtio-comment/202104/msg00013.html
>
> Anton Yakovlev (1):
> ALSA: virtio: add support for audio controls
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2024-02-09 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:36 [v2 PATCH 0/1] ALSA: virtio: add support for audio controls Aiswarya Cyriac
2024-01-15 13:36 ` [v2 PATCH 1/1] " Aiswarya Cyriac
2024-02-19 17:24 ` [v2 PATCH 0/1] " Marcin Radomski
2024-02-20 1:37 ` Anton Yakovlev
2024-02-09 13:01 ` Takashi Iwai [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=877cjd23ln.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=aiswarya.cyriac@opensynergy.com \
--cc=alsa-devel@alsa-project.org \
--cc=anton.yakovlev@opensynergy.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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