From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
Kumar Gala <kumar.gala@linaro.org>,
"andriy.shevchenko@intel.com" <andriy.shevchenko@intel.com>,
xiang xiao <xiaoxiang781216@gmail.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
"liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>, Vinod Koul <vkoul@kernel.org>,
"wendy.liang@xilinx.com" <wendy.liang@xilinx.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Xiang Xiao <xiaoxiang@xiaomi.com>,
Alan Cox <alan@linux.intel.com>,
"sound-open-firmware@alsa-project.org"
<sound-open-firmware@alsa-project.org>
Subject: Re: [v4,00/14] ASoC: Sound Open Firmware (SOF) core
Date: Thu, 21 Feb 2019 17:49:16 -0600 [thread overview]
Message-ID: <e4bef996-db81-afd3-7f32-97e89a3f4319@linux.intel.com> (raw)
In-Reply-To: <20190221112824.GC5970@sirena.org.uk>
>> Just for information... ST Microelectronics plans to port SOF to at
>> least one of its platforms (based on ARM cores). Today, for the
>> co-processor management we use the rpmsg and remoteproc frameworks on
>> the Linux kernel side and OpenAMP on the remote processor side. We are
>> therefore interested in xiang's work.
>> An advantage we see in this generic solution is that compatibility
>> between the Linux kernel frameworks and the OpenAMP library is ensured
>> through discussions in the Linux and OpenAMP communities, involving
>> maintainers and several vendors.
Thanks Arnaud for sharing this information. You made my day. We've had
to deal with a number of hurdles related to platform and tools
availability, so it's good news indeed if there are more platforms
endorsing SOF.
> This is a very good point, especially with people actually jumping on it
> if we can avoid having multiple ABIs to worry about that would make life
> a lot easier. We should at least figure out if it will be disruptive to
> adapt it later on, even if Intel ends up continuing to use a custom
> system integration.
Yes indeed. At a high level we only have very generic send/receive IPC
messages, and it really shouldn't matter how the transport happens.
However the actual contents/semantics of the messages do matter, and
I'll have to run a check to make sure it scales.
next prev parent reply other threads:[~2019-02-21 23:49 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 22:07 [PATCH v4 00/14] ASoC: Sound Open Firmware (SOF) core Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 01/14] ASoC: SOF: Add Sound Open Firmware driver core Pierre-Louis Bossart
2019-02-14 9:25 ` Takashi Iwai
2019-02-14 14:53 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-19 15:38 ` Mark Brown
2019-02-20 14:35 ` Pierre-Louis Bossart
2019-02-20 16:26 ` Mark Brown
2019-02-20 21:32 ` Pierre-Louis Bossart
2019-02-21 18:47 ` Mark Brown
2019-02-22 0:08 ` Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 02/14] ASoC: SOF: Add Sound Open Firmware KControl support Pierre-Louis Bossart
2019-02-14 9:30 ` Takashi Iwai
2019-02-14 14:35 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-14 15:21 ` Takashi Iwai
2019-02-13 22:07 ` [PATCH v4 03/14] ASoC: SOF: Add driver debug support Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 04/14] ASoC: SOF: Add support for IPC IO between DSP and Host Pierre-Louis Bossart
2019-02-14 11:52 ` Takashi Iwai
2019-02-14 14:56 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-20 17:31 ` Mark Brown
2019-02-13 22:07 ` [PATCH v4 05/14] ASoC: SOF: Add PCM operations support Pierre-Louis Bossart
2019-02-14 11:20 ` Takashi Iwai
2019-02-14 15:07 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-14 20:42 ` Pierre-Louis Bossart
2019-02-18 15:51 ` Daniel Baluta
2019-02-13 22:07 ` [PATCH v4 06/14] ASoC: SOF: Add support for loading topologies Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 07/14] ASoC: SOF: Add DSP firmware logger support Pierre-Louis Bossart
2019-02-14 13:19 ` Takashi Iwai
2019-02-14 15:13 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-20 17:44 ` Mark Brown
2019-02-20 20:18 ` Pierre-Louis Bossart
2019-02-21 12:29 ` Andy Shevchenko
2019-02-21 14:57 ` Pierre-Louis Bossart
2019-02-21 15:04 ` Mark Brown
2019-02-13 22:07 ` [PATCH v4 08/14] ASoC: SOF: Add DSP HW abstraction operations Pierre-Louis Bossart
2019-02-14 13:21 ` Takashi Iwai
2019-02-14 15:22 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-14 13:45 ` Andy Shevchenko
2019-02-14 15:21 ` [Sound-open-firmware] " Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 09/14] ASoC: SOF: Add firmware loader support Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 10/14] ASoC: SOF: Add userspace ABI support Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 11/14] ASoC: SOF: Add PM support Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 12/14] ASoC: SOF: Add Nocodec machine driver support Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 13/14] ASoC: SOF: Add xtensa support Pierre-Louis Bossart
2019-02-13 22:07 ` [PATCH v4 14/14] ASoC: SOF: Add utils Pierre-Louis Bossart
2019-02-14 13:33 ` Takashi Iwai
2019-02-14 13:37 ` Takashi Iwai
2019-02-18 20:03 ` [v4,00/14] ASoC: Sound Open Firmware (SOF) core Xiang Xiao
2019-02-19 9:49 ` Srinivas Kandagatla
2019-02-19 15:09 ` xiang xiao
2019-02-19 15:55 ` Pierre-Louis Bossart
2019-02-21 4:39 ` Vinod Koul
2019-02-21 10:42 ` Arnaud Pouliquen
2019-02-21 11:28 ` Mark Brown
2019-02-21 23:49 ` Pierre-Louis Bossart [this message]
2019-02-21 15:27 ` Pierre-Louis Bossart
2019-02-22 8:32 ` xiang xiao
2019-02-22 11:15 ` Keyon Jie
2019-02-22 18:21 ` xiang xiao
2019-02-25 3:05 ` [Sound-open-firmware] [v4, 00/14] " Keyon Jie
2019-02-22 14:48 ` Pierre-Louis Bossart
2019-02-22 18:41 ` xiang xiao
2019-02-22 21:52 ` Pierre-Louis Bossart
2019-02-23 16:42 ` xiang xiao
2019-02-25 10:16 ` Srinivas Kandagatla
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=e4bef996-db81-afd3-7f32-97e89a3f4319@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@intel.com \
--cc=arnaud.pouliquen@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=kumar.gala@linaro.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=sound-open-firmware@alsa-project.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--cc=wendy.liang@xilinx.com \
--cc=xiaoxiang781216@gmail.com \
--cc=xiaoxiang@xiaomi.com \
/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