From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Jayesh Choudhary <j-choudhary@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <devicetree@vger.kernel.org>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <s-vadapalli@ti.com>, <rogerq@kernel.org>,
<afd@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-j721e-main: Make the "scm_conf" node a "simple-bus"
Date: Tue, 3 Jun 2025 15:37:14 +0530 [thread overview]
Message-ID: <0cda49d8-bab3-4197-a6e7-0da39da73bfd@ti.com> (raw)
In-Reply-To: <20250603095609.33569-2-j-choudhary@ti.com>
On Tue, Jun 03, 2025 at 03:26:06PM +0530, Jayesh Choudhary wrote:
> The "scm_conf" bus need not be "syscon". Now that we have "pcie*_ctrl"
> child nodes for "ti,syscon-pcie-ctrl" property in "pcie" nodes, change
> "scm_conf" node to "simple-bus".
> Also remove "reg" property as it is not needed by "simple-bus".
>
> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Regards,
Siddharth.
next prev parent reply other threads:[~2025-06-03 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 9:56 [PATCH 0/4] "scm_conf" node cleanup for TI's Jacinto SoC family Jayesh Choudhary
2025-06-03 9:56 ` [PATCH 1/4] arm64: dts: ti: k3-j721e-main: Make the "scm_conf" node a "simple-bus" Jayesh Choudhary
2025-06-03 10:07 ` Siddharth Vadapalli [this message]
2025-06-03 11:02 ` Krzysztof Kozlowski
2025-06-04 9:48 ` Jayesh Choudhary
2025-07-01 10:23 ` Jayesh Choudhary
2025-07-02 20:30 ` Krzysztof Kozlowski
2025-06-03 9:56 ` [PATCH 2/4] arm64: dts: ti: k3-j7200-main: " Jayesh Choudhary
2025-06-03 10:07 ` Siddharth Vadapalli
2025-06-03 9:56 ` [PATCH 3/4] arm64: dts: ti: k3-j721s2-main: " Jayesh Choudhary
2025-06-03 10:07 ` Siddharth Vadapalli
2025-06-03 9:56 ` [PATCH 4/4] arm64: dts: ti: k3-j784s4-j742s2-main-common: Remove "reg" from "scm_conf" Jayesh Choudhary
2025-06-03 10:07 ` Siddharth Vadapalli
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=0cda49d8-bab3-4197-a6e7-0da39da73bfd@ti.com \
--to=s-vadapalli@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@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=robh@kernel.org \
--cc=rogerq@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;
as well as URLs for NNTP newsgroup(s).