mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Arnd Bergmann <arnd@arndb.de>, Chen-Yu Tsai <wenst@chromium.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	linux-remoteproc@vger.kernel.org,
	Bjorn Andersson <andersson@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v2] remoteproc: mtk_scp: Construct FW path if firmware-name not present
Date: Thu, 30 Oct 2025 10:29:16 +0100	[thread overview]
Message-ID: <141839e6-1dbe-4e98-8412-d47e853d997b@collabora.com> (raw)
In-Reply-To: <f434165f-1717-41ff-93e4-9be5b7fca929@app.fastmail.com>

Il 30/10/25 10:10, Arnd Bergmann ha scritto:
> On Thu, Oct 30, 2025, at 09:21, Chen-Yu Tsai wrote:
>> On Wed, Oct 29, 2025 at 7:05 PM AngeloGioacchino Del Regno
>> <angelogioacchino.delregno@collabora.com> wrote:
>>>
>>>>
>>>> I guess I can send a followup patch?
>>>
>>> The only followup patch that I deem to be necessary is one adding a symlink
>>> or renaming for MT8188's SCP and nothing else.
>>
>> The firmware was uploaded in March of 2025, and is packaged in Debian
>> Trixie, and was also backported to Bookworm. Either adding a symlink or
>> renaming it won't trickle down to users for some time. So this seems
>> like a possible ABI break, where the ABI is the file name.
>>
>> Or maybe you don't consider it as such because SCP hasn't been enabled
>> in the kernel in any release yet?

Just as a clarification:

Exactly, SCP hasn't been enabled in the kernel in any release in the specific
case of MT8188, so this is not breaking anything, and it's not creating any
regression.

> 
> It's normally up to the kernel driver to know about the firmware
> file names and the order of trying the possible fallbacks, which
> is exactly why I originally asked to not rely on the property
> from dtb.
> 
> If you want a symlink in linux-firmware, that would go the other
> way, pointing the old filename to the new location.
> 
>      Arnd

Cheers!
Angelo

  reply	other threads:[~2025-10-30  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15  8:41 AngeloGioacchino Del Regno
2025-10-15 13:41 ` Arnd Bergmann
2025-10-15 13:49   ` AngeloGioacchino Del Regno
2025-10-20 15:18 ` Mathieu Poirier
2025-10-29  9:14 ` Chen-Yu Tsai
2025-10-29 11:05   ` AngeloGioacchino Del Regno
2025-10-30  8:21     ` Chen-Yu Tsai
2025-10-30  9:10       ` Arnd Bergmann
2025-10-30  9:29         ` AngeloGioacchino Del Regno [this message]
2026-01-07 11:12           ` Macpaul Lin (林智斌)
2025-10-30  9:33       ` AngeloGioacchino Del Regno

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=141839e6-1dbe-4e98-8412-d47e853d997b@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=matthias.bgg@gmail.com \
    --cc=wenst@chromium.org \
    /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

all inboxes | Powered by JetHome®