Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Anton Yakovlev <anton.yakovlev@opensynergy.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@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,
	jean-philippe@linaro.org
Subject: Re: [virtio-dev] Re: [PATCH v8] virtio-snd: add virtio sound device specification
Date: Mon, 6 Apr 2020 15:07:44 +0200	[thread overview]
Message-ID: <a1069a63-8213-459f-bda0-fe49ff462433@opensynergy.com> (raw)
In-Reply-To: <20200403105316.urv4wasigr33wxkm@sirius.home.kraxel.org>

Hi,

On 03.04.2020 12:53, Gerd Hoffmann wrote:
>    Hi,
> 
>> This patch proposes virtio specification for a new virtio sound device,
>> that may be useful in case when having audio is required but a device
>> passthrough or emulation is not an option.
>>
>> Signed-off-by: Anton Yakovlev <anton.yakovlev@opensynergy.com>
>> ---
>>
>> v7->v8 changes:
>> 1. Add a universal control request to query information about any
>>     configuration item (jacks, streams and channel maps). The request
>>     allows to get information in one by one or in a batch manner.
>> 2. Add a common information header that allows to link items together
>>     in a unified way.
>> 3. Rework a jack configuration as a jack information structure.
>> 4. Rework a stream configuration as a stream information structure.
>> 5. Make a channel map as a separate item and add the
>>     "Channel Map Control Messages" section.
> 
> Looks good to me.  The new *INFO commands are certainly an improvement.
> I guess you have both guest and host implementations for this meanwhile?

Yes, we do. The driver (v8) is available at the same place:
https://github.com/OpenSynergy/linux/tree/virtio-snd-draft


> 
> take care,
>    Gerd
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
> 
> 

-- 
Anton Yakovlev
Senior Software Engineer

OpenSynergy GmbH
Rotherstr. 20, 10245 Berlin

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2020-04-06 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 16:34 [virtio-dev] [PATCH v8] virtio-snd: add virtio sound device specification Anton Yakovlev
2020-04-03 10:53 ` [virtio-dev] " Gerd Hoffmann
2020-04-06 13:07   ` Anton Yakovlev [this message]
2020-04-14 10:41 ` Anton Yakovlev
2020-04-28 10:15   ` Gerd Hoffmann
2021-01-08 13:56   ` Guennadi Liakhovetski
2021-01-11 14:01     ` Gerd Hoffmann

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=a1069a63-8213-459f-bda0-fe49ff462433@opensynergy.com \
    --to=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=suzuki.poulose@arm.com \
    --cc=tiwai@suse.de \
    --cc=virtio-dev@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