alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	sound-open-firmware@alsa-project.org
Subject: Re: [PATCH v2 00/12] [RESEND] ASoC: SOF DSP virtualisation
Date: Fri, 3 Apr 2020 13:04:05 +0200	[thread overview]
Message-ID: <20200403110404.GA23734@ubuntu> (raw)
In-Reply-To: <20200403092842.GB4286@sirena.org.uk>

Hi Mark,

On Fri, Apr 03, 2020 at 10:28:42AM +0100, Mark Brown wrote:
> On Fri, Apr 03, 2020 at 11:13:54AM +0200, Guennadi Liakhovetski wrote:
> > This patch series extends the SOF driver to add support for DSP
> > virtualisation to ASoC. It is built on top of VirtIO, contains a
> > guest driver and a vhost in-kernel guest driver. This version
> > supports a single playback and a single capture interface on the
> > guest. The specific guest audio topology is supplied by the host
> 
> I've asked a couple of times for documentation of the protocol here but
> don't think I've seen anything yet?

Sorry, we were thinking about the best way to reply. I think Liam will 
provide more procise information. The API we are using is the same as 
what is already used by SOF to communicate with the DSP firmware. With 
VirtIO we re-use the same IPC messages as those, used with the DSP, 
they are just transmitted over Virtual Queues. Additionally to existing 
IPC messages the SOF VirtIO implementation defines 3 more message types 
for topology loading and DSP power management. IPC message types are 
defined in include/sound/sof/header.h, IPC overview is available in 
https://thesofproject.github.io/latest/developer_guides/linux_driver/architecture/sof_driver_arch.html#ipc-processing 
but I'm not aware of a formal SOF IPC protocol documentation.

Thanks
Guennadi

  reply	other threads:[~2020-04-03 11:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  9:13 [PATCH v2 00/12] [RESEND] ASoC: SOF DSP virtualisation Guennadi Liakhovetski
2020-04-03  9:13 ` [PATCH v2 01/12] [RESEND] ASoC: add function parameters to enable forced path pruning Guennadi Liakhovetski
2020-04-03  9:13 ` [PATCH v2 02/12] [RESEND] ASoC: SOF: extract firmware-related operation into a function Guennadi Liakhovetski
2020-04-03  9:13 ` [PATCH v2 03/12] [RESEND] ASoC: SOF: VirtIO: make a function global Guennadi Liakhovetski
2020-04-03  9:13 ` [PATCH v2 04/12] [RESEND] vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl Guennadi Liakhovetski
2020-04-03  9:13 ` [PATCH v2 05/12] [RESEND] ASoC: SOF: support IPC with immediate response Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 06/12] [RESEND] ASoC: SOF: add a power status IPC Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 07/12] [RESEND] ASoC: SOF: add two helper lookup functions Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 08/12] [RESEND] ASoC: SOF: add a VirtIO DSP driver Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 09/12] [RESEND] ASoC: SOF: add a vhost driver: sound part Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 10/12] [RESEND] vhost: add an SOF DSP driver Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 11/12] [RESEND] ASoC: SOF: VirtIO: free guest pipelines upon termination Guennadi Liakhovetski
2020-04-03  9:14 ` [PATCH v2 12/12] [RESEND] ASoC: SOF: VirtIO: enable simultaneous playback and capture Guennadi Liakhovetski
2020-04-03  9:28 ` [PATCH v2 00/12] [RESEND] ASoC: SOF DSP virtualisation Mark Brown
2020-04-03 11:04   ` Guennadi Liakhovetski [this message]
2020-04-03 11:26     ` Mark Brown
2020-04-03 16:10     ` [Sound-open-firmware] " Liam Girdwood
2020-04-03 16:21       ` Mark Brown
2020-04-03 18:09       ` Guennadi Liakhovetski
2020-04-07 11:24         ` Guennadi Liakhovetski
2020-04-07 11:30           ` Mark Brown
2020-04-07 12:44             ` Guennadi Liakhovetski

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=20200403110404.GA23734@ubuntu \
    --to=guennadi.liakhovetski@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.de \
    /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).