From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
sound-open-firmware@alsa-project.org
Subject: Re: [PATCH 0/3] [RESEND] ASoC: SOF: preparatory patches
Date: Tue, 10 Mar 2020 15:13:12 -0500 [thread overview]
Message-ID: <5cdea070-d8ad-9f23-c3f2-b3638e127f7d@linux.intel.com> (raw)
In-Reply-To: <20200310125055.GF4106@sirena.org.uk>
On 3/10/20 7:50 AM, Mark Brown wrote:
> On Mon, Mar 09, 2020 at 05:05:06PM -0500, Pierre-Louis Bossart wrote:
>
>> To get a better picture of the directions, reviewers are invited to take a
>> look at the in-depth documentation written by Guennadi since the initial
>> patches were shared. This documentation was reviewed by Liam and me and is
>> really required to understand the concepts:
>
>> https://thesofproject.github.io/latest/developer_guides/virtualization/virtualization.html
>
> How does this relate to the virtio audio spec that's currently under
> review? It looks to be doing something much lower level than that.
Mark, to avoid any ambiguity, what 'virtio audio spec that's currently
under review' are you referring to?
> 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.
Valid point indeed.
next prev parent reply other threads:[~2020-03-10 20:14 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 [this message]
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
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=5cdea070-d8ad-9f23-c3f2-b3638e127f7d@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=liam.r.girdwood@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