From: Andrew Davis <afd@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>, Andrew Davis <afd@ti.com>
Subject: [PATCH 05/12] arm64: dts: ti: k3-am62: Add reboot-controller node
Date: Wed, 31 Jan 2024 16:19:50 -0600 [thread overview]
Message-ID: <20240131221957.213717-6-afd@ti.com> (raw)
In-Reply-To: <20240131221957.213717-1-afd@ti.com>
While PCSI normally handles reboot for K3, this is an available
fallback in case PCSI reboot fails. Add direct reboot TI-SCI
node to system-controller.
Signed-off-by: Andrew Davis <afd@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index 464b7565d085d..eb71523e85c36 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -203,6 +203,11 @@ k3_reset: reset-controller {
compatible = "ti,sci-reset";
#reset-cells = <2>;
};
+
+ k3_reboot: reboot-controller {
+ bootph-all;
+ compatible = "ti,sci-reboot";
+ };
};
crypto: crypto@40900000 {
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-31 22:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 22:19 [PATCH 00/12] Add TI-SCI reboot driver Andrew Davis
2024-01-31 22:19 ` [PATCH 01/12] dt-bindings: power: reset: Document ti,sci-reboot compatible Andrew Davis
2024-02-01 18:53 ` Conor Dooley
2024-01-31 22:19 ` [PATCH 02/12] dt-bindings: arm: keystone: ti-sci: Add reboot-controller child node Andrew Davis
2024-02-01 18:42 ` Conor Dooley
2024-02-01 23:03 ` Rob Herring
2024-02-01 23:50 ` Andrew Davis
2024-01-31 22:19 ` [PATCH 03/12] power: reset: Add TI-SCI reboot driver Andrew Davis
2024-02-01 21:15 ` Nishanth Menon
2024-02-02 17:04 ` Sebastian Reichel
2024-01-31 22:19 ` [PATCH 04/12] arm64: dts: ti: k3-am64: Add reboot-controller node Andrew Davis
2024-01-31 22:19 ` Andrew Davis [this message]
2024-01-31 22:19 ` [PATCH 06/12] arm64: dts: ti: k3-am62a: " Andrew Davis
2024-01-31 22:19 ` [PATCH 07/12] arm64: dts: ti: k3-am62p: " Andrew Davis
2024-01-31 22:19 ` [PATCH 08/12] arm64: dts: ti: k3-am65: " Andrew Davis
2024-01-31 22:19 ` [PATCH 09/12] arm64: dts: ti: k3-j7200: " Andrew Davis
2024-01-31 22:19 ` [PATCH 10/12] arm64: dts: ti: k3-j721e: " Andrew Davis
2024-01-31 22:19 ` [PATCH 11/12] arm64: dts: ti: k3-j721s2: " Andrew Davis
2024-01-31 22:19 ` [PATCH 12/12] arm64: dts: ti: k3-j784s4: " Andrew Davis
2024-02-01 21:14 ` [PATCH 00/12] Add TI-SCI reboot driver Nishanth Menon
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=20240131221957.213717-6-afd@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=ssantosh@kernel.org \
--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).