From: Nishanth Menon <nm@ti.com>
To: "Padhi, Beleswar" <b-padhi@ti.com>
Cc: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<vigneshr@ti.com>, <kristo@kernel.org>, <afd@ti.com>,
<u-kumar1@ti.com>, <hnagalla@ti.com>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/3] arm64: dts: ti: k3-{j784s4-j742s2/j721s2}-mcu-wakeup: Add HSM M4F node
Date: Tue, 13 Jan 2026 10:29:27 -0600 [thread overview]
Message-ID: <20260113162927.hmf5dnkm44kyefpt@stained> (raw)
In-Reply-To: <8a4692f8-4366-49f2-bcef-b087a7bcc24c@ti.com>
On 21:34-20260113, Padhi, Beleswar wrote:
[...]
> > > + reg-names = "sram0_0", "sram0_1", "sram1";
> > > + resets = <&k3_reset 304 1>;
> > > + firmware-name = "hsm.bin";
> > I am not a fan of putting firmware-name in SoC.dtsi - esp when it is
> > reserved,
>
>
> I thought the opposite way. Since it is reserved (and not a general purpose
> remote core), it is unlikely boards out there are going to use a separate
Fair enough.. I see that the base firmware name is in SoC.dtsi on a per
SoC basis. Agreed that exception can be an override if required
(unlikely in this case). Please document that rationale in the commit
message.
Since we just have a single HSM in each of the SoCs, am62p-hsm-m4f-fw
j722s-hsm-m4f-fw etc in SoC.dtsi would make sense.. just dont do a
generic hsm.bin kind of deal.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
https://ti.com/opensource
next prev parent reply other threads:[~2026-01-13 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 10:47 [PATCH v2 0/3] Add TI K3 HSM M4F nodes in device-tree Beleswar Padhi
2026-01-06 10:47 ` [PATCH v2 1/3] dt-bindings: remoteproc: Add HSM M4F core on TI K3 SoCs Beleswar Padhi
2026-01-07 8:02 ` Krzysztof Kozlowski
2026-01-07 15:35 ` Mathieu Poirier
2026-01-06 10:47 ` [PATCH v2 2/3] arm64: dts: ti: k3-{j784s4-j742s2/j721s2}-mcu-wakeup: Add HSM M4F node Beleswar Padhi
2026-01-09 19:27 ` Nishanth Menon
2026-01-13 16:04 ` Padhi, Beleswar
2026-01-13 16:29 ` Nishanth Menon [this message]
2026-01-06 10:47 ` [PATCH v2 3/3] arm64: dts: ti: k3-am62p-j722s-common-main: " Beleswar Padhi
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=20260113162927.hmf5dnkm44kyefpt@stained \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=b-padhi@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.