From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <afd@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <u-kumar1@ti.com>,
<danishanwar@ti.com>, <srk@ti.com>
Subject: Re: [PATCH v6 5/8] arm64: dts: ti: k3-j722s: Move MAIN domain overrides to k3-j722s-main.dtsi
Date: Fri, 14 Jun 2024 20:29:46 +0530 [thread overview]
Message-ID: <8b06ba3e-f4b2-4654-aaaf-2f15816fff07@ti.com> (raw)
In-Reply-To: <d4c33ee4-1e91-40e5-90c8-bd793bcf34ff@kernel.org>
On Fri, Jun 14, 2024 at 12:53:37PM +0300, Roger Quadros wrote:
> Hi Siddharth,
[...]
> > --- a/arch/arm64/boot/dts/ti/k3-j722s.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-j722s.dtsi
> > @@ -232,14 +232,3 @@ cbass_wakeup: bus@b00000 {
> >
> > /* Include J722S specific peripherals */
> > #include "k3-j722s-main.dtsi"
> > -
> > -/* Main domain overrides */
> > -
> > -&inta_main_dmss {
> > - ti,interrupt-ranges = <7 71 21>;
> > -};
> > -
> > -&oc_sram {
> > - reg = <0x00 0x70000000 0x00 0x40000>;
> > - ranges = <0x00 0x00 0x70000000 0x40000>;
> > -};
> These are originally set in k3-am62p-j722s-common-main.dtsi
> which cannot be as they are not common to both SoCs.
>
> Should we be moving the AM62 specific portion into k3-am62p-main.dtsi.
>
> So they are no longer overrides but SoC specific changes?
Roger,
Thank you for reviewing the patch. I will remove the above properties
within the respective nodes of k3-am62p-j722s-common-main.dtsi and add
them to match the respective SoC in k3-{soc}-main.dtsi.
Regards,
Siddharth.
next prev parent reply other threads:[~2024-06-14 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 13:24 [PATCH v6 0/8] Add PCIe, SERDES and USB DT support for J722S Siddharth Vadapalli
2024-06-12 13:24 ` [PATCH v6 1/8] arm64: dts: ti: am62p: Rename am62p-{}.dtsi to am62p-j722s-common-{}.dtsi Siddharth Vadapalli
2024-06-14 9:45 ` Roger Quadros
2024-06-12 13:24 ` [PATCH v6 2/8] arm64: dts: ti: k3-am62p-j722s: Move AM62P specific USB1 to am62p-main.dtsi Siddharth Vadapalli
2024-06-12 13:24 ` [PATCH v6 3/8] arm64: dts: ti: k3-j722s: Add main domain peripherals specific to J722S Siddharth Vadapalli
2024-06-12 13:24 ` [PATCH v6 4/8] arm64: dts: ti: k3-j722s: Switch to k3-am62p-j722s-common-{}.dtsi includes Siddharth Vadapalli
2024-06-14 9:46 ` Roger Quadros
2024-06-12 13:24 ` [PATCH v6 5/8] arm64: dts: ti: k3-j722s: Move MAIN domain overrides to k3-j722s-main.dtsi Siddharth Vadapalli
2024-06-14 9:53 ` Roger Quadros
2024-06-14 14:59 ` Siddharth Vadapalli [this message]
2024-06-12 13:24 ` [PATCH v6 6/8] arm64: dts: ti: k3-serdes: Add SERDES0/SERDES1 lane-muxing macros for J722S Siddharth Vadapalli
2024-06-12 13:24 ` [PATCH v6 7/8] arm64: dts: ti: k3-j722s-main: Add SERDES and PCIe support Siddharth Vadapalli
2024-06-12 13:24 ` [PATCH v6 8/8] arm64: dts: ti: k3-j722s: Enable PCIe and USB support on J722S-EVM 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=8b06ba3e-f4b2-4654-aaaf-2f15816fff07@ti.com \
--to=s-vadapalli@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--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=nm@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--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 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®