public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>
Cc: Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Santhosh Kumar <s-k6@ti.com>, Bryan Brattlof <bb@ti.com>
Subject: [PATCH 5/5] arm64: dts: ti: k3-am6*: Fix comment in watchdog nodes
Date: Tue, 6 Aug 2024 16:46:04 -0500	[thread overview]
Message-ID: <20240806214605.3379881-6-jm@ti.com> (raw)
In-Reply-To: <20240806214605.3379881-1-jm@ti.com>

The am62ax and am62p devices have an MCU R5F and not an
M4F, the following comment is not correct:

/* Tightly coupled to M4F */

so fix the comment in watchdog nodes.

There is no functional change.

Signed-off-by: Judith Mendez <jm@ti.com>
---
 arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi              | 2 +-
 arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
index cea0e1d4caaa0..a5a33491b51bb 100644
--- a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
@@ -146,7 +146,7 @@ mcu_rti0: watchdog@4880000 {
 		power-domains = <&k3_pds 131 TI_SCI_PD_EXCLUSIVE>;
 		assigned-clocks = <&k3_clks 131 0>;
 		assigned-clock-parents = <&k3_clks 131 2>;
-		/* Tightly coupled to M4F */
+		/* Tightly coupled to R5F */
 		status = "reserved";
 	};
 
diff --git a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi
index d913e6319bad8..d5a498479cba2 100644
--- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi
@@ -154,7 +154,7 @@ mcu_rti0: watchdog@4880000 {
 		power-domains = <&k3_pds 131 TI_SCI_PD_EXCLUSIVE>;
 		assigned-clocks = <&k3_clks 131 0>;
 		assigned-clock-parents = <&k3_clks 131 2>;
-		/* Tightly coupled to M4F */
+		/* Tightly coupled to R5F */
 		status = "reserved";
 	};
 
-- 
2.45.2



      parent reply	other threads:[~2024-08-06 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 21:45 [PATCH 0/5] Fix ESM source interrupts Judith Mendez
2024-08-06 21:46 ` [PATCH 1/5] arm64: dts: ti: k3-am62a: Add ESM support Judith Mendez
2024-08-06 21:46 ` [PATCH 2/5] arm64: dts: ti: k3-am62p: Fix ESM interrupt sources Judith Mendez
2024-08-06 21:46 ` [PATCH 3/5] arm64: dts: ti: k3-am62p: Remove 'reserved' status Judith Mendez
2024-08-07 11:46   ` Nishanth Menon
2024-08-07 15:13     ` Judith Mendez
2024-08-07 15:26       ` Nishanth Menon
2024-08-08 13:37         ` Judith Mendez
2024-08-06 21:46 ` [PATCH 4/5] arm64: dts: ti: k3-am6*: Add comment for ESM interrupt sources Judith Mendez
2024-08-06 21:46 ` Judith Mendez [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=20240806214605.3379881-6-jm@ti.com \
    --to=jm@ti.com \
    --cc=bb@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=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s-k6@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