From: "Kumar, Udit" <u-kumar1@ti.com>
To: Abhash Kumar Jha <a-kumar2@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<conor+dt@kernel.org>, <krzk+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<p-mantena@ti.com>, <m-chawdhry@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH v4 1/2] arm64: dts: ti: k3-j784s4-main.dtsi: Sort the nodes in appropriate order
Date: Tue, 13 Jan 2026 18:41:23 +0530 [thread overview]
Message-ID: <880e6dc2-e4bb-4628-89a4-a487264e4475@ti.com> (raw)
In-Reply-To: <20260112085113.3476193-2-a-kumar2@ti.com>
On 1/12/2026 2:21 PM, Abhash Kumar Jha wrote:
> The device tree nodes should be ordered by unit addresses in ascending
> order.
>
> Correct the order by moving the dsp node at the end as it has a higher unit
> address.
>
> Signed-off-by: Abhash Kumar Jha <a-kumar2@ti.com>
> ---
Please keep clean up as separate patch or series.
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 26 +++++++++++-----------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> index 0160fe0da983..5b7830a3c097 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> @@ -6,19 +6,6 @@
> */
>
> &cbass_main {
> - c71_3: dsp@67800000 {
> - compatible = "ti,j721s2-c71-dsp";
> - reg = <0x00 0x67800000 0x00 0x00080000>,
> - <0x00 0x67e00000 0x00 0x0000c000>;
> - reg-names = "l2sram", "l1dram";
> - resets = <&k3_reset 40 1>;
> - firmware-name = "j784s4-c71_3-fw";
> - ti,sci = <&sms>;
> - ti,sci-dev-id = <40>;
> - ti,sci-proc-ids = <0x33 0xff>;
> - status = "disabled";
> - };
> -
> pcie2_rc: pcie@2920000 {
> compatible = "ti,j784s4-pcie-host";
> reg = <0x00 0x02920000 0x00 0x1000>,
> @@ -113,6 +100,19 @@ serdes2: serdes@5020000 {
> status = "disabled";
> };
> };
> +
> + c71_3: dsp@67800000 {
> + compatible = "ti,j721s2-c71-dsp";
> + reg = <0x00 0x67800000 0x00 0x00080000>,
> + <0x00 0x67e00000 0x00 0x0000c000>;
> + reg-names = "l2sram", "l1dram";
> + resets = <&k3_reset 40 1>;
> + firmware-name = "j784s4-c71_3-fw";
> + ti,sci = <&sms>;
> + ti,sci-dev-id = <40>;
> + ti,sci-proc-ids = <0x33 0xff>;
> + status = "disabled";
> + };
> };
>
> &scm_conf {
next prev parent reply other threads:[~2026-01-13 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 8:51 [PATCH v4 0/2] Refactor watchdog instances for j784s4 and j742s2 Abhash Kumar Jha
2026-01-12 8:51 ` [PATCH v4 1/2] arm64: dts: ti: k3-j784s4-main.dtsi: Sort the nodes in appropriate order Abhash Kumar Jha
2026-01-13 13:11 ` Kumar, Udit [this message]
2026-01-14 16:31 ` Kumar, Udit
2026-01-12 8:51 ` [PATCH v4 2/2] arm64: dts: ti: k3-j784s4-j742s2-main-common.dtsi: Refactor watchdog instances for j784s4 Abhash Kumar Jha
2026-01-13 13:15 ` Kumar, Udit
2026-01-14 17:11 ` [PATCH v4 0/2] Refactor watchdog instances for j784s4 and j742s2 Nishanth Menon
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=880e6dc2-e4bb-4628-89a4-a487264e4475@ti.com \
--to=u-kumar1@ti.com \
--cc=a-kumar2@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.com \
--cc=p-mantena@ti.com \
--cc=robh@kernel.org \
--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