Skip to contentSkip to conversation

Remove ti,sci-sysreset

PATCH In review Andrew Davis 4 participants 9 messages Apr 2, 2024 – Apr 12, 2024

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

cover Remove ti,sci-sysreset

Hello all,

Idea here is to remove one more delta between the U-Boot and Linux DTB files: ti,sci-sysreset. We currently have to add this to every board's -u-boot.dtsi file as this is not a standard node. Instead do what we are moving the kernel towards[0] and remove this node.

Thanks,
Andrew

[0] https://lore.kernel.org/lkml/[email protected]/

Andrew Davis (2):
firmware: ti_sci: Bind sysreset driver when enabled
arm: dts: k3: Remove unneeded ti,sci-sysreset binding and nodes

 arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi  |  7 -----
 .../k3-am625-phyboard-lyra-rdk-u-boot.dtsi    |  7 -----
 .../dts/k3-am625-verdin-wifi-dev-u-boot.dtsi  |  7 -----
 arch/arm/dts/k3-am62a7-sk-u-boot.dtsi         |  4 ---
 arch/arm/dts/k3-am62p5-sk-u-boot.dtsi         |  5 ----
 arch/arm/dts/k3-am642-evm-u-boot.dtsi         |  7 -----
 .../k3-am642-phyboard-electra-rdk-u-boot.dtsi |  4 ---
 arch/arm/dts/k3-am642-sk-u-boot.dtsi          |  7 -----
 .../dts/k3-am65-iot2050-common-u-boot.dtsi    |  4 ---
 .../arm/dts/k3-am68-sk-base-board-u-boot.dtsi |  4 ---
 arch/arm/dts/k3-am69-sk-u-boot.dtsi           |  7 -----
 .../k3-j7200-common-proc-board-u-boot.dtsi    |  4 ---
 .../dts/k3-j721e-beagleboneai64-u-boot.dtsi   |  4 ---
 .../k3-j721e-common-proc-board-u-boot.dtsi    |  4 ---
 arch/arm/dts/k3-j721e-sk-u-boot.dtsi          |  4 ---
 .../k3-j721s2-common-proc-board-u-boot.dtsi   |  4 ---
 arch/arm/dts/k3-j784s4-evm-u-boot.dtsi        |  7 -----
 .../sysreset/ti,sci-sysreset.txt              | 29 -------------------
 drivers/firmware/ti_sci.c                     |  7 +++++
 drivers/sysreset/sysreset-ti-sci.c            |  6 ----
 20 files changed, 7 insertions(+), 125 deletions(-)
 delete mode 100644 doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt
Signature · 1 line
2.39.2
#4 lore raw

PATCH 2/2 arm: dts: k3: Remove unneeded ti, sci-sysreset binding and nodes

This extra binding is non-standard and now unneeded as we bind the sysreset driver automatically. This matches what is done in Linux and allows us to more closely match the DTBs. Remove the binding and all users.

---
 arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi  |  7 -----
 .../k3-am625-phyboard-lyra-rdk-u-boot.dtsi    |  7 -----
 .../dts/k3-am625-verdin-wifi-dev-u-boot.dtsi  |  7 -----
 arch/arm/dts/k3-am62a7-sk-u-boot.dtsi         |  4 ---
 arch/arm/dts/k3-am62p5-sk-u-boot.dtsi         |  5 ----
 arch/arm/dts/k3-am642-evm-u-boot.dtsi         |  7 -----
 .../k3-am642-phyboard-electra-rdk-u-boot.dtsi |  4 ---
 arch/arm/dts/k3-am642-sk-u-boot.dtsi          |  7 -----
 .../dts/k3-am65-iot2050-common-u-boot.dtsi    |  4 ---
 .../arm/dts/k3-am68-sk-base-board-u-boot.dtsi |  4 ---
 arch/arm/dts/k3-am69-sk-u-boot.dtsi           |  7 -----
 .../k3-j7200-common-proc-board-u-boot.dtsi    |  4 ---
 .../dts/k3-j721e-beagleboneai64-u-boot.dtsi   |  4 ---
 .../k3-j721e-common-proc-board-u-boot.dtsi    |  4 ---
 arch/arm/dts/k3-j721e-sk-u-boot.dtsi          |  4 ---
 .../k3-j721s2-common-proc-board-u-boot.dtsi   |  4 ---
 arch/arm/dts/k3-j784s4-evm-u-boot.dtsi        |  7 -----
 .../sysreset/ti,sci-sysreset.txt              | 29 -------------------
 18 files changed, 119 deletions(-)
 delete mode 100644 doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt
arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi +0 -7
index cca0f44b7d8..fb2032068d1 100644
@@ -41,13 +41,6 @@
 	clock-frequency = <25000000>;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &sd_pins_default {
 	/* Force to use SDCD card detect pin */
 	pinctrl-single,pins = <
arch/arm/dts/k3-am625-phyboard-lyra-rdk-u-boot.dtsi +0 -7
index f6138f3058f..94162282068 100644
@@ -42,13 +42,6 @@
 	bootph-all;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &fss {
 	bootph-all;
 };
arch/arm/dts/k3-am625-verdin-wifi-dev-u-boot.dtsi +0 -7
index 28b697b67ae..7fe7ae41543 100644
@@ -85,13 +85,6 @@
 	bootph-all;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &fss {
 	bootph-all;
 };
arch/arm/dts/k3-am62a7-sk-u-boot.dtsi +0 -4
index 31b89b41748..c42dec16194 100644
@@ -119,10 +119,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &vdd_mmc1 {
arch/arm/dts/k3-am62p5-sk-u-boot.dtsi +0 -5
index c166d655390..cf087c6e343 100644
@@ -15,9 +15,4 @@
 
 &dmsc {
 	bootph-pre-ram;
-
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-pre-ram;
-	};
 };
arch/arm/dts/k3-am642-evm-u-boot.dtsi +0 -7
index ee6656774d6..705b3baa81c 100644
@@ -23,13 +23,6 @@
 	bootph-all;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &sdhci0 {
 	bootph-all;
 };
arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi +0 -4
index 5dfc40a843b..4677c35e2d9 100644
@@ -29,10 +29,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &dmss {
arch/arm/dts/k3-am642-sk-u-boot.dtsi +0 -7
index 7e6b2981346..6fcb11bd04d 100644
@@ -15,13 +15,6 @@
 	clock-frequency = <200000000>;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &sdhci0 {
 	status = "disabled";
 };
arch/arm/dts/k3-am65-iot2050-common-u-boot.dtsi +0 -4
index d53f133cd63..b6d2c816acc 100644
@@ -99,10 +99,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-am68-sk-base-board-u-boot.dtsi +0 -4
index 4f34347586e..b8fc62f0dd1 100644
@@ -51,10 +51,6 @@
 
 &sms {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &main_pmx0 {
arch/arm/dts/k3-am69-sk-u-boot.dtsi +0 -7
index bed330e6d4e..4a82d2fd222 100644
@@ -23,13 +23,6 @@
 	bootph-pre-ram;
 };
 
-&sms {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-pre-ram;
-	};
-};
-
 #ifdef CONFIG_TARGET_J784S4_A72_EVM
 
 #define SPL_AM69_SK_DTB "spl/dts/ti/k3-am69-sk.dtb"
arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi +0 -4
index c9fee0ea99b..485f17c5f06 100644
@@ -57,10 +57,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721e-beagleboneai64-u-boot.dtsi +0 -4
index 116ee373118..e202ae16644 100644
@@ -92,10 +92,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi +0 -4
index 9433f3bafae..aa919b40702 100644
@@ -47,10 +47,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721e-sk-u-boot.dtsi +0 -4
index 8b205553cdf..8f4f944263e 100644
@@ -47,10 +47,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721s2-common-proc-board-u-boot.dtsi +0 -4
index a3ebf5996ea..19b2d48c7f8 100644
@@ -51,10 +51,6 @@
 
 &sms {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &main_pmx0 {
arch/arm/dts/k3-j784s4-evm-u-boot.dtsi +0 -7
index ac749782bfc..8f0307321e8 100644
@@ -22,10 +22,3 @@
 		    "tchanrt", "rflow";
 	bootph-pre-ram;
 };
-
-&sms {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-pre-ram;
-	};
-};
doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt deleted +0 -29
deleted file mode 100644
index 02704c6487e..00000000000
@@ -1,29 +0,0 @@
-Texas Instruments TI SCI System Reset Controller
-================================================
-
-Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
-responsible for controlling the state of the IPs that are present.
-Communication between the host processor running an OS and the system
-controller happens through a protocol known as TI SCI [1].
-
-[1] http://processors.wiki.ti.com/index.php/TISCI
-
-System Reset Controller Node
-============================
-The sysreset controller node represents the reset for the overall SoC
-which is managed by the SYSFW. Because this relies on the TI SCI protocol
-to communicate with the SYSFW it must be a child of the sysfw node.
-
-Required Properties:
---------------------
- - compatible: Must be "ti,sci-sysreset"
-
-Example (AM65x):
-----------------
-	sysfw: sysfw {
-		compatible = "ti,am654-system-controller";
-		...
-		k3_sysreset: sysreset-controller {
-			compatible = "ti,sci-sysreset";
-		};
-	};
Signature · 1 line
2.39.2
#1 lore raw

PATCH 1/2 firmware: ti_sci: Bind sysreset driver when enabled

In reply to Andrew Davis

The sysreset TI-SCI API is available with TI-SCI always, there is no need for a DT node to describe the availability of this. If the sysreset driver is available then bind it during ti-sci probe.

Remove the unneeded device tree matching.

---
 drivers/firmware/ti_sci.c          | 7 +++++++
 drivers/sysreset/sysreset-ti-sci.c | 6 ------
 2 files changed, 7 insertions(+), 6 deletions(-)
drivers/firmware/ti_sci.c +7 -0
index ee092185588..6c581b9df9c 100644
@@ -16,6 +16,7 @@
 #include <dm/device.h>
 #include <dm/device_compat.h>
 #include <dm/devres.h>
+#include <dm/lists.h>
 #include <linux/bitops.h>
 #include <linux/compat.h>
 #include <linux/err.h>
@@ -2840,6 +2841,12 @@ static int ti_sci_probe(struct udevice *dev)
 
 	INIT_LIST_HEAD(&info->dev_list);
 
+	if (IS_ENABLED(CONFIG_SYSRESET_TI_SCI)) {
+		ret = device_bind_driver(dev, "ti-sci-sysreset", "sysreset", NULL);
+		if (ret)
+			dev_warn(dev, "cannot bind SYSRESET (ret = %d)\n", ret);
+	}
+
 	return 0;
 }
 
drivers/sysreset/sysreset-ti-sci.c +0 -6
index 5fc05c46cb0..0de132633a8 100644
@@ -60,15 +60,9 @@ static struct sysreset_ops ti_sci_sysreset_ops = {
 	.request = ti_sci_sysreset_request,
 };
 
-static const struct udevice_id ti_sci_sysreset_of_match[] = {
-	{ .compatible = "ti,sci-sysreset", },
-	{ /* sentinel */ },
-};
-
 U_BOOT_DRIVER(ti_sci_sysreset) = {
 	.name = "ti-sci-sysreset",
 	.id = UCLASS_SYSRESET,
-	.of_match = ti_sci_sysreset_of_match,
 	.probe = ti_sci_sysreset_probe,
 	.priv_auto	= sizeof(struct ti_sci_sysreset_data),
 	.ops = &ti_sci_sysreset_ops,
Signature · 1 line
2.39.2
Reviewed-by on v1 1/2
#2 lore raw

Re: [PATCH 1/2] firmware: ti_sci: Bind sysreset driver when enabled

Hi Andrew

Quoted 47 lines · Andrew Davis

The sysreset TI-SCI API is available with TI-SCI always, there is no need for a DT node to describe the availability of this. If the sysreset driver is available then bind it during ti-sci probe.

Remove the unneeded device tree matching.

---
  drivers/firmware/ti_sci.c          | 7 +++++++
  drivers/sysreset/sysreset-ti-sci.c | 6 ------
  2 files changed, 7 insertions(+), 6 deletions(-)
drivers/firmware/ti_sci.c +7 -0
index ee092185588..6c581b9df9c 100644
@@ -16,6 +16,7 @@
  #include <dm/device.h>
  #include <dm/device_compat.h>
  #include <dm/devres.h>
+#include <dm/lists.h>
  #include <linux/bitops.h>
  #include <linux/compat.h>
  #include <linux/err.h>
@@ -2840,6 +2841,12 @@ static int ti_sci_probe(struct udevice *dev)
 
  	INIT_LIST_HEAD(&info->dev_list);
 
+	if (IS_ENABLED(CONFIG_SYSRESET_TI_SCI)) {
+		ret = device_bind_driver(dev, "ti-sci-sysreset", "sysreset", NULL);
+		if (ret)
+			dev_warn(dev, "cannot bind SYSRESET (ret = %d)\n", ret);
+	}
+
  	return 0;
  }
 
drivers/sysreset/sysreset-ti-sci.c +0 -2
index 5fc05c46cb0..0de132633a8 100644
@@ -60,15 +60,9 @@ static struct sysreset_ops ti_sci_sysreset_ops = {
  	.request = ti_sci_sysreset_request,
  };
 
-static const struct udevice_id ti_sci_sysreset_of_match[] = {
-	{ .compatible = "ti,sci-sysreset", },

drivers/sysreset/sysreset-ti-sci.c static struct sysreset_ops ti_sci_sysreset_ops = { · line 68

Quoted 10 lines
drivers/sysreset/sysreset-ti-sci.c +0 -4
-	{ /* sentinel */ },
-};
-
  U_BOOT_DRIVER(ti_sci_sysreset) = {
  	.name = "ti-sci-sysreset",
  	.id = UCLASS_SYSRESET,
-	.of_match = ti_sci_sysreset_of_match,
  	.probe = ti_sci_sysreset_probe,
  	.priv_auto	= sizeof(struct ti_sci_sysreset_data),
  	.ops = &ti_sci_sysreset_ops,
Signature · 2 lines
Thanking You
Neha Malcom Francis
Reviewed-by on v1 2/2
#5 lore raw

Re: [PATCH 2/2] arm: dts: k3: Remove unneeded ti, sci-sysreset binding and nodes

In reply to Andrew Davis

Hi Andrew,

Quoted 28 lines · Andrew Davis

This extra binding is non-standard and now unneeded as we bind the sysreset driver automatically. This matches what is done in Linux and allows us to more closely match the DTBs. Remove the binding and all users.

---
  arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi  |  7 -----
  .../k3-am625-phyboard-lyra-rdk-u-boot.dtsi    |  7 -----
  .../dts/k3-am625-verdin-wifi-dev-u-boot.dtsi  |  7 -----
  arch/arm/dts/k3-am62a7-sk-u-boot.dtsi         |  4 ---
  arch/arm/dts/k3-am62p5-sk-u-boot.dtsi         |  5 ----
  arch/arm/dts/k3-am642-evm-u-boot.dtsi         |  7 -----
  .../k3-am642-phyboard-electra-rdk-u-boot.dtsi |  4 ---
  arch/arm/dts/k3-am642-sk-u-boot.dtsi          |  7 -----
  .../dts/k3-am65-iot2050-common-u-boot.dtsi    |  4 ---
  .../arm/dts/k3-am68-sk-base-board-u-boot.dtsi |  4 ---
  arch/arm/dts/k3-am69-sk-u-boot.dtsi           |  7 -----
  .../k3-j7200-common-proc-board-u-boot.dtsi    |  4 ---
  .../dts/k3-j721e-beagleboneai64-u-boot.dtsi   |  4 ---
  .../k3-j721e-common-proc-board-u-boot.dtsi    |  4 ---
  arch/arm/dts/k3-j721e-sk-u-boot.dtsi          |  4 ---
  .../k3-j721s2-common-proc-board-u-boot.dtsi   |  4 ---
  arch/arm/dts/k3-j784s4-evm-u-boot.dtsi        |  7 -----
  .../sysreset/ti,sci-sysreset.txt              | 29 -------------------
  18 files changed, 119 deletions(-)

delete mode 100644 doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt

[...]

Why not have Kconfig set this as default y if TI_SCI_PROTOCOL set using same argument?

Signature · 2 lines
Thanking You
Neha Malcom Francis
#6 lore raw

Re: [PATCH 2/2] arm: dts: k3: Remove unneeded ti, sci-sysreset binding and nodes

Quoted 32 lines · Neha Malcom Francis

Hi Andrew,

Quoted 25 lines · Andrew Davis

This extra binding is non-standard and now unneeded as we bind the sysreset driver automatically. This matches what is done in Linux and allows us to more closely match the DTBs. Remove the binding and all users.

---
  arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi  |  7 ----- .../k3-am625-phyboard-lyra-rdk-u-boot.dtsi    |  7 ----- .../dts/k3-am625-verdin-wifi-dev-u-boot.dtsi  |  7 -----

  arch/arm/dts/k3-am62a7-sk-u-boot.dtsi         |  4 ---
  arch/arm/dts/k3-am62p5-sk-u-boot.dtsi         |  5 ----
  arch/arm/dts/k3-am642-evm-u-boot.dtsi         |  7 -----

  .../k3-am642-phyboard-electra-rdk-u-boot.dtsi |  4 --- arch/arm/dts/k3-am642-sk-u-boot.dtsi          |  7 ----- .../dts/k3-am65-iot2050-common-u-boot.dtsi    |  4 --- .../arm/dts/k3-am68-sk-base-board-u-boot.dtsi |  4 --- arch/arm/dts/k3-am69-sk-u-boot.dtsi           |  7 ----- .../k3-j7200-common-proc-board-u-boot.dtsi    |  4 --- .../dts/k3-j721e-beagleboneai64-u-boot.dtsi   |  4 --- .../k3-j721e-common-proc-board-u-boot.dtsi    |  4 --- arch/arm/dts/k3-j721e-sk-u-boot.dtsi          |  4 --- .../k3-j721s2-common-proc-board-u-boot.dtsi   |  4 --- arch/arm/dts/k3-j784s4-evm-u-boot.dtsi        |  7 ----- .../sysreset/ti,sci-sysreset.txt              | 29 -------------------

Quoted 3 lines
  18 files changed, 119 deletions(-)

  delete mode 100644 doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt

Quoted 6 lines

[...]

Why not have Kconfig set this as default y if TI_SCI_PROTOCOL set using same argument?

Good idea, and the same could probably be said for most TI-SCI based drivers.

We might also look into adding more of these as "imply" under config ARCH_K3, all K3 boards will want/need these. Should help simplify our defconfig.

Andrew

Tested-by on v1 1/2
#3 lore raw

Re: [PATCH 1/2] firmware: ti_sci: Bind sysreset driver when enabled

In reply to Andrew Davis
Quoted 59 lines · Andrew Davis

The sysreset TI-SCI API is available with TI-SCI always, there is no need for a DT node to describe the availability of this. If the sysreset driver is available then bind it during ti-sci probe.

Remove the unneeded device tree matching.

---
 drivers/firmware/ti_sci.c          | 7 +++++++
 drivers/sysreset/sysreset-ti-sci.c | 6 ------
 2 files changed, 7 insertions(+), 6 deletions(-)
drivers/firmware/ti_sci.c +7 -0
index ee092185588..6c581b9df9c 100644
@@ -16,6 +16,7 @@
 #include <dm/device.h>
 #include <dm/device_compat.h>
 #include <dm/devres.h>
+#include <dm/lists.h>
 #include <linux/bitops.h>
 #include <linux/compat.h>
 #include <linux/err.h>
@@ -2840,6 +2841,12 @@ static int ti_sci_probe(struct udevice *dev)
 
 	INIT_LIST_HEAD(&info->dev_list);
 
+	if (IS_ENABLED(CONFIG_SYSRESET_TI_SCI)) {
+		ret = device_bind_driver(dev, "ti-sci-sysreset", "sysreset", NULL);
+		if (ret)
+			dev_warn(dev, "cannot bind SYSRESET (ret = %d)\n", ret);
+	}
+
 	return 0;
 }
 
drivers/sysreset/sysreset-ti-sci.c +0 -6
index 5fc05c46cb0..0de132633a8 100644
@@ -60,15 +60,9 @@ static struct sysreset_ops ti_sci_sysreset_ops = {
 	.request = ti_sci_sysreset_request,
 };
 
-static const struct udevice_id ti_sci_sysreset_of_match[] = {
-	{ .compatible = "ti,sci-sysreset", },
-	{ /* sentinel */ },
-};
-
 U_BOOT_DRIVER(ti_sci_sysreset) = {
 	.name = "ti-sci-sysreset",
 	.id = UCLASS_SYSRESET,
-	.of_match = ti_sci_sysreset_of_match,
 	.probe = ti_sci_sysreset_probe,
 	.priv_auto	= sizeof(struct ti_sci_sysreset_data),
 	.ops = &ti_sci_sysreset_ops,
Signature · 1 line
2.39.2
Tested-by on v1 2/2
#7 lore raw

Re: [PATCH 2/2] arm: dts: k3: Remove unneeded ti, sci-sysreset binding and nodes

In reply to Andrew Davis
Quoted 337 lines · Andrew Davis

This extra binding is non-standard and now unneeded as we bind the sysreset driver automatically. This matches what is done in Linux and allows us to more closely match the DTBs. Remove the binding and all users.

---
 arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi  |  7 -----
 .../k3-am625-phyboard-lyra-rdk-u-boot.dtsi    |  7 -----
 .../dts/k3-am625-verdin-wifi-dev-u-boot.dtsi  |  7 -----
 arch/arm/dts/k3-am62a7-sk-u-boot.dtsi         |  4 ---
 arch/arm/dts/k3-am62p5-sk-u-boot.dtsi         |  5 ----
 arch/arm/dts/k3-am642-evm-u-boot.dtsi         |  7 -----
 .../k3-am642-phyboard-electra-rdk-u-boot.dtsi |  4 ---
 arch/arm/dts/k3-am642-sk-u-boot.dtsi          |  7 -----
 .../dts/k3-am65-iot2050-common-u-boot.dtsi    |  4 ---
 .../arm/dts/k3-am68-sk-base-board-u-boot.dtsi |  4 ---
 arch/arm/dts/k3-am69-sk-u-boot.dtsi           |  7 -----
 .../k3-j7200-common-proc-board-u-boot.dtsi    |  4 ---
 .../dts/k3-j721e-beagleboneai64-u-boot.dtsi   |  4 ---
 .../k3-j721e-common-proc-board-u-boot.dtsi    |  4 ---
 arch/arm/dts/k3-j721e-sk-u-boot.dtsi          |  4 ---
 .../k3-j721s2-common-proc-board-u-boot.dtsi   |  4 ---
 arch/arm/dts/k3-j784s4-evm-u-boot.dtsi        |  7 -----
 .../sysreset/ti,sci-sysreset.txt              | 29 -------------------
 18 files changed, 119 deletions(-)
 delete mode 100644 doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt
arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi +0 -7
index cca0f44b7d8..fb2032068d1 100644
@@ -41,13 +41,6 @@
 	clock-frequency = <25000000>;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &sd_pins_default {
 	/* Force to use SDCD card detect pin */
 	pinctrl-single,pins = <
arch/arm/dts/k3-am625-phyboard-lyra-rdk-u-boot.dtsi +0 -7
index f6138f3058f..94162282068 100644
@@ -42,13 +42,6 @@
 	bootph-all;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &fss {
 	bootph-all;
 };
arch/arm/dts/k3-am625-verdin-wifi-dev-u-boot.dtsi +0 -7
index 28b697b67ae..7fe7ae41543 100644
@@ -85,13 +85,6 @@
 	bootph-all;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &fss {
 	bootph-all;
 };
arch/arm/dts/k3-am62a7-sk-u-boot.dtsi +0 -4
index 31b89b41748..c42dec16194 100644
@@ -119,10 +119,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &vdd_mmc1 {
arch/arm/dts/k3-am62p5-sk-u-boot.dtsi +0 -5
index c166d655390..cf087c6e343 100644
@@ -15,9 +15,4 @@
 
 &dmsc {
 	bootph-pre-ram;
-
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-pre-ram;
-	};
 };
arch/arm/dts/k3-am642-evm-u-boot.dtsi +0 -7
index ee6656774d6..705b3baa81c 100644
@@ -23,13 +23,6 @@
 	bootph-all;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &sdhci0 {
 	bootph-all;
 };
arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi +0 -4
index 5dfc40a843b..4677c35e2d9 100644
@@ -29,10 +29,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &dmss {
arch/arm/dts/k3-am642-sk-u-boot.dtsi +0 -7
index 7e6b2981346..6fcb11bd04d 100644
@@ -15,13 +15,6 @@
 	clock-frequency = <200000000>;
 };
 
-&dmsc {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
-};
-
 &sdhci0 {
 	status = "disabled";
 };
arch/arm/dts/k3-am65-iot2050-common-u-boot.dtsi +0 -4
index d53f133cd63..b6d2c816acc 100644
@@ -99,10 +99,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-am68-sk-base-board-u-boot.dtsi +0 -4
index 4f34347586e..b8fc62f0dd1 100644
@@ -51,10 +51,6 @@
 
 &sms {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &main_pmx0 {
arch/arm/dts/k3-am69-sk-u-boot.dtsi +0 -7
index bed330e6d4e..4a82d2fd222 100644
@@ -23,13 +23,6 @@
 	bootph-pre-ram;
 };
 
-&sms {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-pre-ram;
-	};
-};
-
 #ifdef CONFIG_TARGET_J784S4_A72_EVM
 
 #define SPL_AM69_SK_DTB "spl/dts/ti/k3-am69-sk.dtb"
arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi +0 -4
index c9fee0ea99b..485f17c5f06 100644
@@ -57,10 +57,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721e-beagleboneai64-u-boot.dtsi +0 -4
index 116ee373118..e202ae16644 100644
@@ -92,10 +92,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi +0 -4
index 9433f3bafae..aa919b40702 100644
@@ -47,10 +47,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721e-sk-u-boot.dtsi +0 -4
index 8b205553cdf..8f4f944263e 100644
@@ -47,10 +47,6 @@
 
 &dmsc {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &k3_pds {
arch/arm/dts/k3-j721s2-common-proc-board-u-boot.dtsi +0 -4
index a3ebf5996ea..19b2d48c7f8 100644
@@ -51,10 +51,6 @@
 
 &sms {
 	bootph-all;
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-all;
-	};
 };
 
 &main_pmx0 {
arch/arm/dts/k3-j784s4-evm-u-boot.dtsi +0 -7
index ac749782bfc..8f0307321e8 100644
@@ -22,10 +22,3 @@
 		    "tchanrt", "rflow";
 	bootph-pre-ram;
 };
-
-&sms {
-	k3_sysreset: sysreset-controller {
-		compatible = "ti,sci-sysreset";
-		bootph-pre-ram;
-	};
-};
doc/device-tree-bindings/sysreset/ti,sci-sysreset.txt deleted +0 -29
deleted file mode 100644
index 02704c6487e..00000000000
@@ -1,29 +0,0 @@
-Texas Instruments TI SCI System Reset Controller
-================================================
-
-Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
-responsible for controlling the state of the IPs that are present.
-Communication between the host processor running an OS and the system
-controller happens through a protocol known as TI SCI [1].
-
-[1] http://processors.wiki.ti.com/index.php/TISCI
-
-System Reset Controller Node
-============================
-The sysreset controller node represents the reset for the overall SoC
-which is managed by the SYSFW. Because this relies on the TI SCI protocol
-to communicate with the SYSFW it must be a child of the sysfw node.
-
-Required Properties:
---------------------
- - compatible: Must be "ti,sci-sysreset"
-
-Example (AM65x):
-----------------
-	sysfw: sysfw {
-		compatible = "ti,am654-system-controller";
-		...
-		k3_sysreset: sysreset-controller {
-			compatible = "ti,sci-sysreset";
-		};
-	};
Signature · 1 line
2.39.2
#8 lore raw
In reply to Andrew Davis
Quoted 9 lines · Andrew Davis

Idea here is to remove one more delta between the U-Boot and Linux DTB files: ti,sci-sysreset. We currently have to add this to every board's -u-boot.dtsi file as this is not a standard node. Instead do what we are moving the kernel towards[0] and remove this node.

Thanks,
Andrew

[...]

Applied to u-boot/master, thanks!

Signature · 1 line
Tom