From: Nishanth Menon <nm@ti.com>
To: "Raghavendra, Vignesh" <vigneshr@ti.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-j721e-mcu-wakeup: Switch to "ti,j721e-system-controller" compatible
Date: Mon, 5 Jun 2023 15:52:20 -0500 [thread overview]
Message-ID: <20230605205220.rjmcsi5tjn4auqa7@arose> (raw)
In-Reply-To: <4b4f4eef-398b-843b-37f8-fdf97c1b6b8d@ti.com>
On 20:43-20230605, Vignesh Raghavendra wrote:
> Hi
>
> On 4/24/2023 9:18 PM, Nishanth Menon wrote:
> > Switch to "ti,j721e-system-controller" compatible to be more specific.
> >
> > Signed-off-by: Nishanth Menon <nm@ti.com>
> > ---
> > arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> > index 24e8125db8c4..71b8b04a7789 100644
> > --- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> > @@ -35,7 +35,7 @@ k3_reset: reset-controller {
> > };
> >
> > mcu_conf: syscon@40f00000 {
> > - compatible = "syscon", "simple-mfd";
> > + compatible = "ti,j721e-system-controller", "syscon", "simple-mfd";
> > reg = <0x0 0x40f00000 0x0 0x20000>;
> > #address-cells = <1>;
> > #size-cells = <1>;
>
> As Andrew suggested at [0], lets work on getting rid of unneeded
> "syscon" here and move to simple-bus instead
>
> [0] https://lore.kernel.org/all/76da0b98-3274-b047-db11-ecabc117ae11@ti.com/
OK. Let me relook at the following series as well:
https://lore.kernel.org/all/20230424144949.244135-1-nm@ti.com/
-> AM65x dtbs_check warning fixups??
https://lore.kernel.org/all/20230424154841.353631-1-nm@ti.com/
-> J721e dtbs_check warning fixups??
https://lore.kernel.org/linux-arm-kernel/20230424173623.477577-1-nm@ti.com/
-> J7200 dtbs_check warning fixups??
I will try and respond/ respin the relevant patchsets.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-05 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:48 [PATCH 0/2] arm64: dts: ti: k3-j721e: dtbs_check warnings fixups Nishanth Menon
2023-04-24 15:48 ` [PATCH 1/2] arm64: dts: ti: k3-j721e-mcu-wakeup: Switch to "ti,j721e-system-controller" compatible Nishanth Menon
2023-06-05 15:13 ` Raghavendra, Vignesh
2023-06-05 20:52 ` Nishanth Menon [this message]
2023-04-24 15:48 ` [PATCH 2/2] arm64: dts: ti: k3-j721e-mcu-wakeup: Fix fss node name Nishanth Menon
2023-06-06 16:14 ` [PATCH 0/2] arm64: dts: ti: k3-j721e: dtbs_check warnings fixups 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=20230605205220.rjmcsi5tjn4auqa7@arose \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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