* [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage
@ 2021-05-21 22:24 Grygorii Strashko
2021-05-21 22:24 ` [PATCH 1/3] ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios Grygorii Strashko
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: Grygorii Strashko @ 2021-05-21 22:24 UTC (permalink / raw)
To: Tony Lindgren
Cc: linux-kernel, linux-omap, devicetree, Rob Herring, Grygorii Strashko
The ti,no-reset-on-init flag need to be at the interconnect target module
level for the modules that have it defined.
The ti-sysc driver handles this case, but produces warning, not a critical
issue.
Grygorii Strashko (3):
ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios
ARM: dts: am437x-gp-evm: fix ti,no-reset-on-init flag for gpios
ARM: dts: am335x: fix ti,no-reset-on-init flag for gpios
arch/arm/boot/dts/am335x-baltos.dtsi | 4 ++--
arch/arm/boot/dts/am335x-evmsk.dts | 2 +-
arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi | 2 +-
arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi | 2 +-
arch/arm/boot/dts/am33xx-l4.dtsi | 2 +-
arch/arm/boot/dts/am437x-gp-evm.dts | 5 ++++-
arch/arm/boot/dts/am437x-l4.dtsi | 2 +-
arch/arm/boot/dts/am57xx-cl-som-am57x.dts | 5 ++---
arch/arm/boot/dts/dra7-l4.dtsi | 4 ++--
9 files changed, 15 insertions(+), 13 deletions(-)
--
2.17.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH 1/3] ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios
2021-05-21 22:24 [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Grygorii Strashko
@ 2021-05-21 22:24 ` Grygorii Strashko
2021-05-21 22:24 ` [PATCH 2/3] ARM: dts: am437x-gp-evm: " Grygorii Strashko
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Grygorii Strashko @ 2021-05-21 22:24 UTC (permalink / raw)
To: Tony Lindgren
Cc: linux-kernel, linux-omap, devicetree, Rob Herring, Grygorii Strashko
The ti,no-reset-on-init flag need to be at the interconnect target module
level for the modules that have it defined.
The ti-sysc driver handles this case, but produces warning, not a critical
issue.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
---
arch/arm/boot/dts/am57xx-cl-som-am57x.dts | 5 ++---
arch/arm/boot/dts/dra7-l4.dtsi | 4 ++--
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/am57xx-cl-som-am57x.dts b/arch/arm/boot/dts/am57xx-cl-som-am57x.dts
index 0d5fe2bfb683..39eba2bc36dd 100644
--- a/arch/arm/boot/dts/am57xx-cl-som-am57x.dts
+++ b/arch/arm/boot/dts/am57xx-cl-som-am57x.dts
@@ -610,12 +610,11 @@
>;
};
-&gpio3 {
- status = "okay";
+&gpio3_target {
ti,no-reset-on-init;
};
-&gpio2 {
+&gpio2_target {
status = "okay";
ti,no-reset-on-init;
};
diff --git a/arch/arm/boot/dts/dra7-l4.dtsi b/arch/arm/boot/dts/dra7-l4.dtsi
index 149144cdff35..6e33c0bf32a9 100644
--- a/arch/arm/boot/dts/dra7-l4.dtsi
+++ b/arch/arm/boot/dts/dra7-l4.dtsi
@@ -1343,7 +1343,7 @@
};
};
- target-module@55000 { /* 0x48055000, ap 13 0e.0 */
+ gpio2_target: target-module@55000 { /* 0x48055000, ap 13 0e.0 */
compatible = "ti,sysc-omap2", "ti,sysc";
reg = <0x55000 0x4>,
<0x55010 0x4>,
@@ -1376,7 +1376,7 @@
};
};
- target-module@57000 { /* 0x48057000, ap 15 06.0 */
+ gpio3_target: target-module@57000 { /* 0x48057000, ap 15 06.0 */
compatible = "ti,sysc-omap2", "ti,sysc";
reg = <0x57000 0x4>,
<0x57010 0x4>,
--
2.17.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [PATCH 2/3] ARM: dts: am437x-gp-evm: fix ti,no-reset-on-init flag for gpios
2021-05-21 22:24 [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Grygorii Strashko
2021-05-21 22:24 ` [PATCH 1/3] ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios Grygorii Strashko
@ 2021-05-21 22:24 ` Grygorii Strashko
2021-05-21 22:24 ` [PATCH 3/3] ARM: dts: am335x: " Grygorii Strashko
2021-05-27 12:07 ` [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Tony Lindgren
3 siblings, 0 replies; 5+ messages in thread
From: Grygorii Strashko @ 2021-05-21 22:24 UTC (permalink / raw)
To: Tony Lindgren
Cc: linux-kernel, linux-omap, devicetree, Rob Herring, Grygorii Strashko
The ti,no-reset-on-init flag need to be at the interconnect target module
level for the modules that have it defined.
The ti-sysc driver handles this case, but produces warning, not a critical
issue.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
---
arch/arm/boot/dts/am437x-gp-evm.dts | 5 ++++-
arch/arm/boot/dts/am437x-l4.dtsi | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
index 6e4d05d649e9..033b984ff637 100644
--- a/arch/arm/boot/dts/am437x-gp-evm.dts
+++ b/arch/arm/boot/dts/am437x-gp-evm.dts
@@ -813,11 +813,14 @@
status = "okay";
};
+&gpio5_target {
+ ti,no-reset-on-init;
+};
+
&gpio5 {
pinctrl-names = "default";
pinctrl-0 = <&display_mux_pins>;
status = "okay";
- ti,no-reset-on-init;
p8 {
/*
diff --git a/arch/arm/boot/dts/am437x-l4.dtsi b/arch/arm/boot/dts/am437x-l4.dtsi
index e217ffc09770..a6f19ae7d3e6 100644
--- a/arch/arm/boot/dts/am437x-l4.dtsi
+++ b/arch/arm/boot/dts/am437x-l4.dtsi
@@ -2070,7 +2070,7 @@
};
};
- target-module@22000 { /* 0x48322000, ap 116 64.0 */
+ gpio5_target: target-module@22000 { /* 0x48322000, ap 116 64.0 */
compatible = "ti,sysc-omap2", "ti,sysc";
reg = <0x22000 0x4>,
<0x22010 0x4>,
--
2.17.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [PATCH 3/3] ARM: dts: am335x: fix ti,no-reset-on-init flag for gpios
2021-05-21 22:24 [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Grygorii Strashko
2021-05-21 22:24 ` [PATCH 1/3] ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios Grygorii Strashko
2021-05-21 22:24 ` [PATCH 2/3] ARM: dts: am437x-gp-evm: " Grygorii Strashko
@ 2021-05-21 22:24 ` Grygorii Strashko
2021-05-27 12:07 ` [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Tony Lindgren
3 siblings, 0 replies; 5+ messages in thread
From: Grygorii Strashko @ 2021-05-21 22:24 UTC (permalink / raw)
To: Tony Lindgren
Cc: linux-kernel, linux-omap, devicetree, Rob Herring, Grygorii Strashko
The ti,no-reset-on-init flag need to be at the interconnect target module
level for the modules that have it defined.
The ti-sysc driver handles this case, but produces warning, not a critical
issue.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
---
arch/arm/boot/dts/am335x-baltos.dtsi | 4 ++--
arch/arm/boot/dts/am335x-evmsk.dts | 2 +-
arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi | 2 +-
arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi | 2 +-
arch/arm/boot/dts/am33xx-l4.dtsi | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-baltos.dtsi b/arch/arm/boot/dts/am335x-baltos.dtsi
index 3ea286180382..1103a2cb836f 100644
--- a/arch/arm/boot/dts/am335x-baltos.dtsi
+++ b/arch/arm/boot/dts/am335x-baltos.dtsi
@@ -393,10 +393,10 @@
status = "okay";
};
-&gpio0 {
+&gpio0_target {
ti,no-reset-on-init;
};
-&gpio3 {
+&gpio3_target {
ti,no-reset-on-init;
};
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts b/arch/arm/boot/dts/am335x-evmsk.dts
index d5f8d5e2eb5d..45bf0273ecd8 100644
--- a/arch/arm/boot/dts/am335x-evmsk.dts
+++ b/arch/arm/boot/dts/am335x-evmsk.dts
@@ -646,7 +646,7 @@
status = "okay";
};
-&gpio0 {
+&gpio0_target {
ti,no-reset-on-init;
};
diff --git a/arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi b/arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi
index 4e90f9c23d2e..8121a199607c 100644
--- a/arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi
+++ b/arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi
@@ -150,7 +150,7 @@
status = "okay";
};
-&gpio0 {
+&gpio0_target {
ti,no-reset-on-init;
};
diff --git a/arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi b/arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi
index 98d8ed4ad967..39e5d2ce600a 100644
--- a/arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi
+++ b/arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi
@@ -353,7 +353,7 @@
status = "okay";
};
-&gpio0 {
+&gpio0_target {
ti,no-reset-on-init;
};
diff --git a/arch/arm/boot/dts/am33xx-l4.dtsi b/arch/arm/boot/dts/am33xx-l4.dtsi
index 039a9ab4c7ea..dcce5e3e001e 100644
--- a/arch/arm/boot/dts/am33xx-l4.dtsi
+++ b/arch/arm/boot/dts/am33xx-l4.dtsi
@@ -1789,7 +1789,7 @@
};
};
- target-module@ae000 { /* 0x481ae000, ap 56 3a.0 */
+ gpio3_target: target-module@ae000 { /* 0x481ae000, ap 56 3a.0 */
compatible = "ti,sysc-omap2", "ti,sysc";
reg = <0xae000 0x4>,
<0xae010 0x4>,
--
2.17.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage
2021-05-21 22:24 [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Grygorii Strashko
` (2 preceding siblings ...)
2021-05-21 22:24 ` [PATCH 3/3] ARM: dts: am335x: " Grygorii Strashko
@ 2021-05-27 12:07 ` Tony Lindgren
3 siblings, 0 replies; 5+ messages in thread
From: Tony Lindgren @ 2021-05-27 12:07 UTC (permalink / raw)
To: Grygorii Strashko; +Cc: linux-kernel, linux-omap, devicetree, Rob Herring
* Grygorii Strashko <grygorii.strashko@ti.com> [210522 01:24]:
> The ti,no-reset-on-init flag need to be at the interconnect target module
> level for the modules that have it defined.
> The ti-sysc driver handles this case, but produces warning, not a critical
> issue.
Thanks for doing this, applying all into omap-for-v5.14/dt.
Tony
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-05-27 12:08 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-21 22:24 [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Grygorii Strashko
2021-05-21 22:24 ` [PATCH 1/3] ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios Grygorii Strashko
2021-05-21 22:24 ` [PATCH 2/3] ARM: dts: am437x-gp-evm: " Grygorii Strashko
2021-05-21 22:24 ` [PATCH 3/3] ARM: dts: am335x: " Grygorii Strashko
2021-05-27 12:07 ` [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Tony Lindgren
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.