From: Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Daniel Baluta" <daniel.baluta@nxp.com>,
"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Alper Nebi Yasak" <alpernebiyasak@gmail.com>,
"Syed Saba Kareem" <Syed.SabaKareem@amd.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Marian Postevca" <posteuca@mutex.one>,
"Vijendar Mukunda" <Vijendar.Mukunda@amd.com>,
"V sujith kumar Reddy" <Vsujithkumar.Reddy@amd.com>,
"Mastan Katragadda" <Mastan.Katragadda@amd.com>,
"Ajit Kumar Pandey" <AjitKumar.Pandey@amd.com>,
"Hiregoudar, Basavaraj" <Basavaraj.Hiregoudar@amd.com>,
"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
sound-open-firmware@alsa-project.org, kernel@collabora.com
Subject: Re: [PATCH 07/11] ASoC: SOF: core: Skip firmware test for undefined fw_name
Date: Thu, 14 Dec 2023 18:58:28 +0530 [thread overview]
Message-ID: <97d68467-5580-4faf-b94e-7efd030d0a73@amd.com> (raw)
In-Reply-To: <2c09e01b-777b-48ac-adf9-63d61e1a36fc@linux.intel.com>
On 12/14/23 17:27, Péter Ujfalusi wrote:
>
> On 14/12/2023 12:58, Venkata Prasad Potturu wrote:
>> On 12/14/23 16:18, Péter Ujfalusi wrote:
>> Thanks for your time Peter!
>>> On 09/12/2023 22:53, Cristian Ciocaltea wrote:
>>>> Some SOF drivers like AMD ACP do not always rely on a single static
>>>> firmware file, but may require multiple files having their names
>>>> dynamically computed on probe time, e.g. based on chip name.
>>> I see, AMD vangogh needs two binary files to be loaded sometimes, it
>>> is not using the default name as it hints via the sof_dev_desc
>>> ("sof-vangogh.ri").
>>>
>>> The constructed names for the two files are just using different pattern:
>>> sof-%PLAT%.ri
>>> vs
>>> sof-%PLAT%-code.bin
>>> sof-%PLAT%-data.bin
>>>
>>> iow, instead of the combined .ri file which includes the code and data
>>> segment it has 'raw' bin files and cannot use the core for loading the
>>> firmware.
>>>
>>> What is the reason for this? an .ri file can have two 'modules' one to
>>> be written to IRAM the other to DRAM.
>>> sof_ipc3_load_fw_to_dsp()
>> For AMD Vangogh platform devices signed firmware image is required, so
>> split .ri image into code and data images.
>>
>> Only Code.bin will be signed and loaded into corresponding IRAM location.
> This is not different than what the Intel .ri files are made of. The
> module which is to be loaded to IRAM is signed code the module which
> goes to DRAM is not signed.
> The loader itself is not looking into the sections of the .ri image, it
> just parses the header and copies them where they belong.
>
> if the issue is name collision then you could try to put the signed
> firmware file under 'signed' folder (fw_path_postfix) of the platform
> like Intel does with the community signed ones?
We have a limitation that code image can't be signed during compilation.
So splitting the .ri image into code and data bin and sign the code bin
and load into IRAM.
>
> It would be great if somehow we can handle all of these in core, have
> shared code and familiar prints among vendors, platforms..
>
> Fwiw, I'm planning the path, filename creation to be moved to core for
> the current platforms, but it implies that they do use single firmware file.
> struct sof_dev_desc would only have two strings:
> vendor - AMD / iMX / Intel / Mediatek
> platform - tgl, vaggogh, etc
>
> I need to adjust it based on what I have learned today about vangogh.
>
next prev parent reply other threads:[~2023-12-14 13:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 20:53 [PATCH 00/11] Improve SOF support for Steam Deck OLED Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 01/11] ASoC: amd: acp: Drop redundant initialization of machine driver data Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 02/11] ASoC: amd: acp: Make use of existing *_CODEC_DAI macros Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 03/11] ASoC: amd: acp: Add missing error handling in sof-mach Cristian Ciocaltea
2023-12-11 13:31 ` Emil Velikov
2023-12-11 16:56 ` Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 04/11] ASoC: amd: acp: Update MODULE_DESCRIPTION for sof-mach Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 05/11] ASoC: SOF: amd: Fix memory leak in amd_sof_acp_probe() Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 06/11] ASoC: SOF: amd: Optimize quirk for Valve Galileo Cristian Ciocaltea
2023-12-10 3:33 ` Venkata Prasad Potturu
2023-12-10 8:42 ` Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 07/11] ASoC: SOF: core: Skip firmware test for undefined fw_name Cristian Ciocaltea
2023-12-14 10:48 ` Péter Ujfalusi
2023-12-14 10:58 ` Venkata Prasad Potturu
2023-12-14 11:57 ` Péter Ujfalusi
2023-12-14 13:28 ` Venkata Prasad Potturu [this message]
2023-12-14 11:29 ` Cristian Ciocaltea
2023-12-14 11:35 ` Péter Ujfalusi
2023-12-14 11:40 ` Cristian Ciocaltea
2023-12-14 11:52 ` Péter Ujfalusi
2023-12-14 11:51 ` Péter Ujfalusi
2023-12-14 11:58 ` Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 08/11] ASoC: SOF: amd: Override default fw name for Valve Galileo Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 09/11] ASoC: SOF: amd: Compute file paths on firmware load Cristian Ciocaltea
2023-12-10 3:50 ` Venkata Prasad Potturu
2023-12-10 8:56 ` Cristian Ciocaltea
2023-12-09 20:53 ` [PATCH 10/11] ASoC: amd: acp: Use correct DAI link ID for BT codec Cristian Ciocaltea
2023-12-10 3:24 ` Venkata Prasad Potturu
2023-12-10 9:06 ` Cristian Ciocaltea
2023-12-10 10:05 ` Venkata Prasad Potturu
2023-12-10 10:32 ` Cristian Ciocaltea
2023-12-11 5:48 ` Venkata Prasad Potturu
2023-12-09 20:53 ` [PATCH 11/11] ASoC: SOF: topology: Add new DAI type entry for SOF_DAI_AMD_BT Cristian Ciocaltea
2023-12-10 3:30 ` Venkata Prasad Potturu
2023-12-10 9:08 ` Cristian Ciocaltea
2023-12-10 9:51 ` Venkata Prasad Potturu
2023-12-10 10:12 ` Cristian Ciocaltea
2023-12-10 14:01 ` Mark Brown
2023-12-10 15:50 ` Cristian Ciocaltea
2023-12-11 5:58 ` Venkata Prasad Potturu
2023-12-14 12:23 ` Cristian Ciocaltea
2023-12-14 12:36 ` Venkata Prasad Potturu
2023-12-14 13:15 ` Venkata Prasad Potturu
2023-12-14 16:42 ` Cristian Ciocaltea
2023-12-15 9:58 ` Venkata Prasad Potturu
2023-12-15 10:57 ` Cristian Ciocaltea
2023-12-15 12:53 ` Mark Brown
2023-12-12 6:41 ` Mukunda,Vijendar
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=97d68467-5580-4faf-b94e-7efd030d0a73@amd.com \
--to=venkataprasad.potturu@amd.com \
--cc=AjitKumar.Pandey@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mastan.Katragadda@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Syed.SabaKareem@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=Vsujithkumar.Reddy@amd.com \
--cc=alpernebiyasak@gmail.com \
--cc=broonie@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kernel@collabora.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=posteuca@mutex.one \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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;
as well as URLs for NNTP newsgroup(s).