All of lore.kernel.org
 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 0/3] [RESEND] ASoC: SOF: preparatory patches
Date: Thu, 12 Mar 2020 14:09:34 +0100	[thread overview]
Message-ID: <20200312130933.GD15167@ubuntu> (raw)
In-Reply-To: <20200312121549.GB4038@sirena.org.uk>

On Thu, Mar 12, 2020 at 12:15:49PM +0000, Mark Brown wrote:
> On Thu, Mar 12, 2020 at 12:45:37PM +0100, Guennadi Liakhovetski wrote:
> > On Tue, Mar 10, 2020 at 12:50:56PM +0000, Mark Brown wrote:
> 
> > > How does this relate to the virtio audio spec that's currently under
> > > review?
> 
> > The spec under discussion is only for simple audio virtualisation with fixed 
> > roles and topologies. With our approach guests get access to advanced DSP 
> > capabilities. The virtualisation approach under discussion can be a fallback 
> > for cases when no DSP has been detected on the host.
> 
> So they're orthogonal :/  Have you proposed your spec yet?
> 
> > > It looks to be doing something much lower level than that.
> > > I am concerned that this looks to be exposing DPCM as a virtio ABI,
> > > we're trying to replace it as an internal API never mind ABI.
> 
> > You mean that our approach works at the widget level, which is a part of the 
> > DPCM API? Well there is a translation layer between our ABI and DPCM. And by 
> > virtue of the same argument don't we already have DPCM as an ABI on the 
> > opposite side of SOF - in its IPC ABI? Largely this virtualisation approach 
> > doesn't add new interfaces, it re-uses the SOF IPC ABI, which is also one of 
> > its advantages.
> 
> Please bear in mind that the page you linked to is very high level and
> I've not seen the actual spec or anything.  The page and your mails both
> talk about DPCM so it sounds like that's a part of the interface.

Let me rebase my current stack and post it here, stay tuned :-)

Thanks
Guennadi

      reply	other threads:[~2020-03-12 13:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 17:07 [PATCH 0/3] [RESEND] ASoC: SOF: preparatory patches Guennadi Liakhovetski
2020-03-09 17:07 ` [PATCH 1/3] ASoC: (cosmetic) simplify dpcm_prune_paths() Guennadi Liakhovetski
2020-03-09 21:37   ` Pierre-Louis Bossart
2020-03-09 17:07 ` [PATCH 2/3] ASoC: add function parameters to enable forced path pruning Guennadi Liakhovetski
2020-03-09 21:48   ` Pierre-Louis Bossart
2020-03-10 12:45   ` Mark Brown
2020-03-11  7:41     ` Guennadi Liakhovetski
2020-03-11 12:25       ` Mark Brown
2020-03-11 12:36         ` Guennadi Liakhovetski
2020-03-11 12:41           ` Mark Brown
2020-03-11 13:26             ` Guennadi Liakhovetski
2020-03-09 17:07 ` [PATCH 3/3] ASoC: export DPCM runtime update functions Guennadi Liakhovetski
2020-03-09 21:54   ` [Sound-open-firmware] " Pierre-Louis Bossart
2020-03-09 22:05 ` [PATCH 0/3] [RESEND] ASoC: SOF: preparatory patches Pierre-Louis Bossart
2020-03-10 12:50   ` Mark Brown
2020-03-10 20:13     ` Pierre-Louis Bossart
2020-03-11 12:16       ` Mark Brown
2020-03-12 11:45     ` Guennadi Liakhovetski
2020-03-12 12:15       ` Mark Brown
2020-03-12 13:09         ` Guennadi Liakhovetski [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=20200312130933.GD15167@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.