From: Anton Yakovlev <anton.yakovlev@opensynergy.com>
To: "Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "jasowang@redhat.com" <jasowang@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>
Subject: Re: [PATCH 0/7] ALSA: add virtio sound driver
Date: Sun, 24 Jan 2021 17:53:52 +0100 [thread overview]
Message-ID: <52efab17-d6e2-c3f4-c3de-73338b811534@opensynergy.com> (raw)
In-Reply-To: <3ac230040630c3b6695f8a091e000f5b4f90b3ce.camel@intel.com>
Hi, Liam!
On 20.01.2021 11:10, Girdwood, Liam R wrote:
> CAUTION: This email originated from outside of the organization.
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> Hi Anton,
>
> On Wed, 2021-01-20 at 01:36 +0100, Anton Yakovlev wrote:
>> This series implements a driver part of the virtio sound device
>> specification v8 [1].
>>
>> The driver supports PCM playback and capture substreams, jack and
>> channel map controls. A message-based transport is used to write/read
>> PCM frames to/from a device.
>>
>> The series is based (and was actually tested) on Linus's master
>> branch [2], on top of
>>
>> commit 1e2a199f6ccd ("Merge tag 'spi-fix-v5.11-rc4' of ...")
>>
>> As a device part was used OpenSynergy proprietary implementation.
>>
>> Any comments are very welcome.
>>
>
> This just looks like the guest front end here, do you have a follow up
> series for the host backend ?
As I mentioned in the cover message, as a device part was used our own
proprietary implementation. And there are no plans to upstream that
part.
> Thanks
>
> Liam
> ---------------------------------------------------------------------
> Intel Corporation (UK) Limited
> Registered No. 1134945 (England)
> Registered Office: Pipers Way, Swindon SN3 1RJ
> VAT No: 860 2173 47
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
--
Anton Yakovlev
Senior Software Engineer
OpenSynergy GmbH
Rotherstr. 20, 10245 Berlin
Phone: +49 30 60 98 54 0
E-Mail: anton.yakovlev@opensynergy.com
www.opensynergy.com
Handelsregister/Commercial Registry: Amtsgericht Charlottenburg, HRB 108616B
Geschäftsführer/Managing Director: Regis Adjamah
prev parent reply other threads:[~2021-01-24 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 0:36 [PATCH 0/7] ALSA: add virtio sound driver Anton Yakovlev
2021-01-20 0:36 ` [PATCH 1/7] uapi: virtio_ids: add a sound device type ID from OASIS spec Anton Yakovlev
2021-01-20 0:36 ` [PATCH 2/7] uapi: virtio_snd: add the sound device header file Anton Yakovlev
2021-01-20 8:19 ` Michael S. Tsirkin
2021-01-20 8:35 ` Michael S. Tsirkin
2021-01-24 16:36 ` Anton Yakovlev
2021-01-20 8:32 ` Michael S. Tsirkin
2021-01-20 0:36 ` [PATCH 3/7] ALSA: virtio: add virtio sound driver Anton Yakovlev
2021-01-20 8:26 ` Michael S. Tsirkin
2021-01-24 16:48 ` Anton Yakovlev
2021-01-20 0:36 ` [PATCH 4/7] ALSA: virtio: handling control and I/O messages for the PCM device Anton Yakovlev
2021-01-20 8:29 ` Michael S. Tsirkin
2021-01-24 16:49 ` Anton Yakovlev
2021-01-20 0:36 ` [PATCH 5/7] ALSA: virtio: PCM substream operators Anton Yakovlev
2021-01-20 8:36 ` Michael S. Tsirkin
2021-01-24 16:51 ` Anton Yakovlev
2021-01-20 0:36 ` [PATCH 6/7] ALSA: virtio: introduce jack support Anton Yakovlev
2021-01-20 0:36 ` [PATCH 7/7] ALSA: virtio: introduce device suspend/resume support Anton Yakovlev
2021-01-20 10:10 ` [PATCH 0/7] ALSA: add virtio sound driver Girdwood, Liam R
2021-01-24 16:53 ` Anton Yakovlev [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=52efab17-d6e2-c3f4-c3de-73338b811534@opensynergy.com \
--to=anton.yakovlev@opensynergy.com \
--cc=alsa-devel@alsa-project.org \
--cc=jasowang@redhat.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).