Add TI-SCI reboot driver
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest12 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/12 | dt-bindings: power: reset: Document ti,sci-reboot compatibleDocumentation/ MAINTAINERS | +34 | 1 reply | |
| 2/12 | dt-bindings: arm: keystone: ti-sci: Add reboot-controller child nodeDocumentation/ | +8 | 3 replies | |
| 3/12 | power: reset: Add TI-SCI reboot driverMAINTAINERS drivers/ drivers/ +1 more | +72 | 2 replies | |
| 4/12 | arm64: dts: ti: k3-am64: Add reboot-controller nodearch/ | +5 | 0 replies | |
| 5/12 | arm64: dts: ti: k3-am62: Add reboot-controller nodearch/ | +5 | 0 replies | |
| 6/12 | arm64: dts: ti: k3-am62a: Add reboot-controller nodearch/ | +4 | 0 replies | |
| 7/12 | arm64: dts: ti: k3-am62p: Add reboot-controller nodearch/ | +5 | 0 replies | |
| 8/12 | arm64: dts: ti: k3-am65: Add reboot-controller nodearch/ | +4 | 0 replies | |
| 9/12 | arm64: dts: ti: k3-j7200: Add reboot-controller nodearch/ | +4 | 0 replies | |
| 10/12 | arm64: dts: ti: k3-j721e: Add reboot-controller nodearch/ | +4 | 0 replies | |
| 11/12 | arm64: dts: ti: k3-j721s2: Add reboot-controller nodearch/ | +4 | 0 replies | |
| 12/12 | arm64: dts: ti: k3-j784s4: Add reboot-controller nodearch/ | +5 | 0 replies |
Reviews trailers per patch
3 of 12 patches have a Reviewed-by or Acked-by.
| Patch | Conor Dooley | Nishanth Menon |
|---|---|---|
| 1/12 | A-b | |
| 2/12 | A-b | |
| 3/12 | R-b | |
| 4/12 | ||
| 5/12 | ||
| 6/12 | ||
| 7/12 | ||
| 8/12 | ||
| 9/12 | ||
| 10/12 | ||
| 11/12 | ||
| 12/12 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 00/12] Add TI-SCI reboot driver
Hello all,
While PCSI normally handles reboot for K3, this is an available fallback in case PCSI reboot fails. This driver is registered with low priority as we want PSCI to remain the main way these devices are rebooted.
The important part is the binding/DT changes. Currently in U-Boot (which use the Linux device trees) we may not have PSCI available yet (pre TF-A) and so we need this node to correctly reboot. Adding this node in U-Boot is one of the last remaining deltas between the two project DT files.
Thanks,
Andrew
Andrew Davis (12):
dt-bindings: power: reset: Document ti,sci-reboot compatible
dt-bindings: arm: keystone: ti-sci: Add reboot-controller child node
power: reset: Add TI-SCI reboot driver
arm64: dts: ti: k3-am64: Add reboot-controller node
arm64: dts: ti: k3-am62: Add reboot-controller node
arm64: dts: ti: k3-am62a: Add reboot-controller node
arm64: dts: ti: k3-am62p: Add reboot-controller node
arm64: dts: ti: k3-am65: Add reboot-controller node
arm64: dts: ti: k3-j7200: Add reboot-controller node
arm64: dts: ti: k3-j721e: Add reboot-controller node
arm64: dts: ti: k3-j721s2: Add reboot-controller node
arm64: dts: ti: k3-j784s4: Add reboot-controller node
.../bindings/arm/keystone/ti,sci.yaml | 8 +++ .../bindings/power/reset/ti,sci-reboot.yaml | 33 ++++++++++ MAINTAINERS | 2 + arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 5 ++ arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 4 ++ arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 5 ++ arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 5 ++ arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 5 ++ drivers/power/reset/Kconfig | 7 +++ drivers/power/reset/Makefile | 1 + drivers/power/reset/ti-sci-reboot.c | 63 +++++++++++++++++++ 15 files changed, 154 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/reset/ti,sci-reboot.yaml create mode 100644 drivers/power/reset/ti-sci-reboot.c
Signature · 1 line
2.39.2