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@xxxxxx>
---
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
