From: Bryan Brattlof <bb@ti.com>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <praneeth@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<khasim@ti.com>, <v-singh1@ti.com>, <afd@ti.com>,
<devarsht@ti.com>
Subject: Re: [PATCHv4 5/6] arm64: dts: ti: Update firmware-name for IPC
Date: Mon, 23 Jun 2025 09:29:52 -0500 [thread overview]
Message-ID: <20250623142952.3aeec366w2lmoswv@bryanbrattlof.com> (raw)
In-Reply-To: <20250623141253.3519546-6-p-bhagat@ti.com>
On June 23, 2025 thus sayeth Paresh Bhagat:
> Update the firmware-name properties in the dts file to point to new IPC
> firmware binaries for both the mcu-r5 and c7x core.
>
Same here. This seems like we should have squashed this into 4/6
~Bryan
> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62d2-evm.dts | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62d2-evm.dts b/arch/arm64/boot/dts/ti/k3-am62d2-evm.dts
> index 8fde89ecba67..c98e4c98c956 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62d2-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62d2-evm.dts
> @@ -487,6 +487,7 @@ &mcu_r5fss0_core0 {
> mboxes = <&mailbox0_cluster2 &mbox_mcu_r5_0>;
> memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
> <&mcu_r5fss0_core0_memory_region>;
> + firmware-name = "am62d-mcu-r5f0_0-fw";
> };
>
> &c7x_0 {
> @@ -495,6 +496,7 @@ &c7x_0 {
> mboxes = <&mailbox0_cluster1 &mbox_c7x_0>;
> memory-region = <&c7x_0_dma_memory_region>,
> <&c7x_0_memory_region>;
> + firmware-name = "am62d-c71_0-fw";
> };
>
> &cpsw3g {
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-06-23 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 14:12 [PATCHv4 0/6] Add support for AM62D2 SoC and EVM Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 1/6] arm64: dts: ti: Add bootph property to nodes at source for am62a Paresh Bhagat
2025-06-23 14:45 ` Bryan Brattlof
2025-06-24 9:13 ` Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 2/6] dt-bindings: arm: ti: Add bindings for AM62D2 SoC Paresh Bhagat
2025-06-23 14:25 ` Krzysztof Kozlowski
2025-06-24 10:39 ` Paresh Bhagat
2025-06-24 10:55 ` Krzysztof Kozlowski
2025-06-24 11:21 ` Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 3/6] arm64: dts: ti: Add pinctrl entries for AM62D2 family of SoCs Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 4/6] arm64: dts: ti: Add support for AM62D2-EVM Paresh Bhagat
2025-06-24 8:21 ` Andrew Lunn
2025-06-26 8:24 ` [EXTERNAL] " Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 5/6] arm64: dts: ti: Update firmware-name for IPC Paresh Bhagat
2025-06-23 14:29 ` Bryan Brattlof [this message]
2025-06-24 9:12 ` Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 6/6] arm64: dts: ti: Add eMMC support for AM62D Paresh Bhagat
2025-06-23 14:28 ` Bryan Brattlof
2025-06-24 9:11 ` Paresh Bhagat
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=20250623142952.3aeec366w2lmoswv@bryanbrattlof.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khasim@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=nm@ti.com \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=v-singh1@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 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®