linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>, <nm@ti.com>,
	<vigneshr@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>, <srk@ti.com>
Subject: Re: [PATCH 13/13] arm64: dts: ti: k3-j721s2-mcu-wakeup: Disable "mcu_cpsw" in the SoC file
Date: Fri, 30 May 2025 10:26:28 +0530	[thread overview]
Message-ID: <62c3a4e6-ffa3-4fc4-a0b1-c8b4bbec684b@ti.com> (raw)
In-Reply-To: <4d2eeedb-0b3e-485c-ba15-82fb78fca4c7@kernel.org>

On Thu, May 29, 2025 at 03:38:10PM +0200, Krzysztof Kozlowski wrote:
> On 29/05/2025 15:34, Siddharth Vadapalli wrote:
> > Following the existing convention of disabling nodes in the SoC file and
> > enabling only the required ones in the board file, disable "mcu_cpsw" node.
> > 
> > Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> > ---
> >  arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> Really all of this is fake split. One line per commit.

I split the patches into Board and SoC specific changes. I was following
the split used when we add new device-tree nodes:
- Add the node to SoC file in the first commit
- Enable it in the Board file in the next commit

Since this is a cleanup, the above split may not be required and I
understand that. I will squash the changes in the next version of this
series.

Thank you for your feedback.

Regards,
Siddharth.

      reply	other threads:[~2025-05-30  4:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 13:34 [PATCH 00/13] TI-K3-DTS: Cleanup CPSW DT Nodes Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 01/13] arm64: dts: ti: k3-am625-beagleplay: Enable "cpsw3g" in the board file Siddharth Vadapalli
2025-05-29 13:37   ` Krzysztof Kozlowski
2025-05-30  4:52     ` Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 02/13] arm64: dts: ti: k3-am62-lp-sk: " Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 03/13] arm64: dts: ti: k3-am625-sk: " Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 04/13] arm64: dts: ti: k3-am62-main: Disable "cpsw3g" in the SoC file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 05/13] arm64: dts: ti: k3-am654-base-board: Enable "mcu_cpsw" in board file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 06/13] arm64: dts: ti: k3-am65-mcu: Disable "mcu_cpsw" in the SoC file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 07/13] arm64: dts: ti: iot2050-common: Remove redundant "mcu_cpsw" node status Siddharth Vadapalli
2025-05-29 13:38   ` Krzysztof Kozlowski
2025-05-30  4:54     ` Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 08/13] arm64: dts: ti: k3-j7200-common-proc-board: Enable "mcu_cpsw" in board file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 09/13] arm64: dts: ti: k3-j7200-mcu-wakeup: Disable "mcu_cpsw" in the SoC file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 10/13] arm64: dts: ti: k3-j721e-common-proc-board: Enable "mcu_cpsw" in board file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 11/13] arm64: dts: ti: k3-j721e-mcu-wakeup: Disable "mcu_cpsw" in the SoC file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 12/13] arm64: dts: ti: k3-j721s2-common-proc-board: Enable "mcu_cpsw" in board file Siddharth Vadapalli
2025-05-29 13:34 ` [PATCH 13/13] arm64: dts: ti: k3-j721s2-mcu-wakeup: Disable "mcu_cpsw" in the SoC file Siddharth Vadapalli
2025-05-29 13:38   ` Krzysztof Kozlowski
2025-05-30  4:56     ` Siddharth Vadapalli [this message]

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=62c3a4e6-ffa3-4fc4-a0b1-c8b4bbec684b@ti.com \
    --to=s-vadapalli@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=srk@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;
as well as URLs for NNTP newsgroup(s).