From: Aniket Limaye <a-limaye@ti.com>
To: Manorit Chawdhry <m-chawdhry@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Neha Malcom Francis <n-francis@ti.com>,
Udit Kumar <u-kumar1@ti.com>, Beleswar Padhi <b-padhi@ti.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Andrew Davis <afd@ti.com>
Subject: Re: [PATCH v5 02/12] arm64: dts: ti: k3-j784s4-j742s2-mcu-wakeup: Remove parent nodes bootph-*
Date: Wed, 23 Oct 2024 21:08:56 +0530 [thread overview]
Message-ID: <47441421-23d4-42a9-b080-21f7c9314fa6@ti.com> (raw)
In-Reply-To: <20241023-b4-upstream-bootph-all-v5-2-a974d06370ab@ti.com>
On 23/10/24 12:27, Manorit Chawdhry wrote:
> Adding bootph properties on leaf nodes imply that they are applicable to
> the parent nodes as well. Bootloaders can derive the parent nodes when
> bootph is available in the leaf nodes.
>
> Remove the bootph-* properties from parent nodes as they are redundant.
>
> Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Reviewed-by: Aniket Limaye <a-limaye@ti.com>
> ---
>
> Notes:
> It wasn't existing previously in U-boot but the following patch fixes it [0]
>
> [0]: https://lore.kernel.org/u-boot/20231217163627.2339802-10-sjg@chromium.org/
>
> arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi
> index 9899da73a905..46bc2a3e4aea 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-j742s2-mcu-wakeup-common.dtsi
> @@ -7,7 +7,6 @@
>
> &cbass_mcu_wakeup {
> sms: system-controller@44083000 {
> - bootph-all;
> compatible = "ti,k2g-sci";
> ti,host-id = <12>;
>
> @@ -39,7 +38,6 @@ k3_reset: reset-controller {
> };
>
> wkup_conf: bus@43000000 {
> - bootph-all;
> compatible = "simple-bus";
> #address-cells = <1>;
> #size-cells = <1>;
> @@ -458,7 +456,6 @@ mcu_spi2: spi@40320000 {
> };
>
> mcu_navss: bus@28380000 {
> - bootph-all;
> compatible = "simple-bus";
> #address-cells = <2>;
> #size-cells = <2>;
>
next prev parent reply other threads:[~2024-10-23 15:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 6:57 [PATCH v5 00/12] Add bootph-all property for J7 boards Manorit Chawdhry
2024-10-23 6:57 ` [PATCH v5 01/12] arm64: dts: ti: k3-j784s4-j742s2-mcu-wakeup: Move bootph from mcu_timer1 to mcu_timer0 Manorit Chawdhry
2024-10-23 6:57 ` [PATCH v5 02/12] arm64: dts: ti: k3-j784s4-j742s2-mcu-wakeup: Remove parent nodes bootph-* Manorit Chawdhry
2024-10-23 15:38 ` Aniket Limaye [this message]
2024-10-23 6:57 ` [PATCH v5 03/12] arm64: dts: ti: k3-j784s4: Add bootph-* properties Manorit Chawdhry
2024-10-23 6:57 ` [PATCH v5 04/12] arm64: dts: ti: k3-j721s2: " Manorit Chawdhry
2024-10-23 6:57 ` [PATCH v5 05/12] arm64: dts: ti: k3-j721e: " Manorit Chawdhry
2024-10-23 11:24 ` Neha Malcom Francis
2024-10-23 6:57 ` [PATCH v5 06/12] arm64: dts: ti: k3-j7200: " Manorit Chawdhry
2024-10-23 15:05 ` Aniket Limaye
2024-10-23 6:57 ` [PATCH v5 07/12] arm64: dts: ti: k3-j784s4-j742s2-evm-common: Remove parent nodes bootph-* Manorit Chawdhry
2024-10-23 15:25 ` Aniket Limaye
2024-10-23 6:57 ` [PATCH v5 08/12] arm64: dts: ti: k3-j721s2-evm*: Add bootph-* properties Manorit Chawdhry
2024-10-23 6:57 ` [PATCH v5 09/12] arm64: dts: ti: k3-am68-sk*: " Manorit Chawdhry
2024-10-23 6:57 ` [PATCH v5 10/12] arm64: dts: ti: k3-j721e-evm*: " Manorit Chawdhry
2024-10-23 11:33 ` Neha Malcom Francis
2024-10-23 6:57 ` [PATCH v5 11/12] arm64: dts: ti: k3-j721e-sk*: " Manorit Chawdhry
2024-10-23 11:34 ` Neha Malcom Francis
2024-10-23 6:57 ` [PATCH v5 12/12] arm64: dts: ti: k3-j7200-evm*: " Manorit Chawdhry
2024-10-23 15:05 ` Aniket Limaye
2024-10-23 16:22 ` Aniket Limaye
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=47441421-23d4-42a9-b080-21f7c9314fa6@ti.com \
--to=a-limaye@ti.com \
--cc=afd@ti.com \
--cc=b-padhi@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=n-francis@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@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®