From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 21 Feb 2019 11:28:24 +0000 From: Mark Brown Subject: Re: [alsa-devel] [v4,00/14] ASoC: Sound Open Firmware (SOF) core Message-ID: <20190221112824.GC5970@sirena.org.uk> References: <20190213220734.10471-1-pierre-louis.bossart@linux.intel.com> <1550520188-9253-1-git-send-email-xiaoxiang@xiaomi.com> <2ad7bf66-a0a9-b97d-e1b1-48e3f9c699c5@linaro.org> <20190221043925.GF2736@vkoul-mobl> <1af21f7e-1ea1-98a0-cf6d-74d0f4e5b186@st.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vEao7xgI/oilGqZ+" Content-Disposition: inline In-Reply-To: <1af21f7e-1ea1-98a0-cf6d-74d0f4e5b186@st.com> To: Arnaud Pouliquen Cc: Vinod Koul , Pierre-Louis Bossart , xiang xiao , Srinivas Kandagatla , Daniel Baluta , Kumar Gala , "andriy.shevchenko@intel.com" , "alsa-devel@alsa-project.org" , "tiwai@suse.de" , "linux-remoteproc@vger.kernel.org" , Bjorn Andersson , "liam.r.girdwood@linux.intel.com" , Xiang Xiao , "sound-open-firmware@alsa-project.org" , "wendy.liang@xilinx.com" , Alan Cox List-ID: --vEao7xgI/oilGqZ+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 21, 2019 at 11:42:25AM +0100, Arnaud Pouliquen wrote: > On 2/21/19 5:39 AM, Vinod Koul wrote: > > On 19-02-19, 09:55, Pierre-Louis Bossart wrote: > >> On 2/19/19 9:09 AM, xiang xiao wrote: > > Rather than evolve the IPC, i would say it makes more sense that we > > "reuse" existing upstream frameworks.. As given below by xiang > > this seems to have support for RTOSes (see point 4 below) and looking at > > below it seems to have much better coverage across systems. > > This should also help in easy adoption of SoF for non Intel people... > > Also looking at it, lot of IPC code, DSP loading etc would go away > > making SoF code lesser in footprint. > > I think benefits outweigh the effort of porting to a framework which is > > already upstream and used on many platforms for different vendors! > 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. 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. --vEao7xgI/oilGqZ+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlxui1cACgkQJNaLcl1U h9Af6gf9EDATFZKplMkYwZcj1R2AQS86EbQOhKcGcedXfpPHtM1W1Y0b1jzpvMD6 r8GHrfbNhkZ5PDF5aetBsbHbg5kfyd8kgt1X/rOBnAaJx9hymExKvLKwJfmvU/Eb mT7/vMbHsgVXhEwXsoPpzfuSJUeaZUX3754qPrezZqx4qiTrQyeePoJcrHeppf7k eOjie8M3i/lrRCtRa71ZjsPyTT8UR65DzQorAsEcn1LjjRlFEk425Kp+jXj0Ii64 XIhEp/TQxco3f79GEffO7uTU7de7Nu00/Af+SNXcmSphnnb2/5K7ihWFT4IFT9/W nWHAwEWDGmCJTwJH8ZO5bMXdJtLdBQ== =9xY7 -----END PGP SIGNATURE----- --vEao7xgI/oilGqZ+-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [v4,00/14] ASoC: Sound Open Firmware (SOF) core Date: Thu, 21 Feb 2019 11:28:24 +0000 Message-ID: <20190221112824.GC5970@sirena.org.uk> References: <20190213220734.10471-1-pierre-louis.bossart@linux.intel.com> <1550520188-9253-1-git-send-email-xiaoxiang@xiaomi.com> <2ad7bf66-a0a9-b97d-e1b1-48e3f9c699c5@linaro.org> <20190221043925.GF2736@vkoul-mobl> <1af21f7e-1ea1-98a0-cf6d-74d0f4e5b186@st.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5187247186776168898==" Return-path: In-Reply-To: <1af21f7e-1ea1-98a0-cf6d-74d0f4e5b186@st.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" To: Arnaud Pouliquen Cc: Daniel Baluta , Kumar Gala , "andriy.shevchenko@intel.com" , "alsa-devel@alsa-project.org" , xiang xiao , "tiwai@suse.de" , "linux-remoteproc@vger.kernel.org" , Pierre-Louis Bossart , Bjorn Andersson , "liam.r.girdwood@linux.intel.com" , Vinod Koul , "wendy.liang@xilinx.com" , Srinivas Kandagatla , Xiang Xiao , Alan Cox , "sound-open-firmware@alsa-project.org" List-Id: alsa-devel@alsa-project.org --===============5187247186776168898== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vEao7xgI/oilGqZ+" Content-Disposition: inline --vEao7xgI/oilGqZ+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 21, 2019 at 11:42:25AM +0100, Arnaud Pouliquen wrote: > On 2/21/19 5:39 AM, Vinod Koul wrote: > > On 19-02-19, 09:55, Pierre-Louis Bossart wrote: > >> On 2/19/19 9:09 AM, xiang xiao wrote: > > Rather than evolve the IPC, i would say it makes more sense that we > > "reuse" existing upstream frameworks.. As given below by xiang > > this seems to have support for RTOSes (see point 4 below) and looking at > > below it seems to have much better coverage across systems. > > This should also help in easy adoption of SoF for non Intel people... > > Also looking at it, lot of IPC code, DSP loading etc would go away > > making SoF code lesser in footprint. > > I think benefits outweigh the effort of porting to a framework which is > > already upstream and used on many platforms for different vendors! > 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. 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. --vEao7xgI/oilGqZ+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlxui1cACgkQJNaLcl1U h9Af6gf9EDATFZKplMkYwZcj1R2AQS86EbQOhKcGcedXfpPHtM1W1Y0b1jzpvMD6 r8GHrfbNhkZ5PDF5aetBsbHbg5kfyd8kgt1X/rOBnAaJx9hymExKvLKwJfmvU/Eb mT7/vMbHsgVXhEwXsoPpzfuSJUeaZUX3754qPrezZqx4qiTrQyeePoJcrHeppf7k eOjie8M3i/lrRCtRa71ZjsPyTT8UR65DzQorAsEcn1LjjRlFEk425Kp+jXj0Ii64 XIhEp/TQxco3f79GEffO7uTU7de7Nu00/Af+SNXcmSphnnb2/5K7ihWFT4IFT9/W nWHAwEWDGmCJTwJH8ZO5bMXdJtLdBQ== =9xY7 -----END PGP SIGNATURE----- --vEao7xgI/oilGqZ+-- --===============5187247186776168898== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============5187247186776168898==--