Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sander Vanheule <sander@svanheule.net>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sander Vanheule <sander@svanheule.net>
Subject: [PATCH 9/9] mips: dts: realtek: Add restart to Cisco SG220-26P
Date: Sun, 19 Jan 2025 19:34:24 +0100	[thread overview]
Message-ID: <20250119183424.259353-10-sander@svanheule.net> (raw)
In-Reply-To: <20250119183424.259353-1-sander@svanheule.net>

Define a gpio-restart node to the Cisco SG220-26P so the device can be
rebooted using the SoC's hard reset pin. Set the priority to 192 so the
gpio-restart method takes priority over the watchdog restart.

Signed-off-by: Sander Vanheule <sander@svanheule.net>
---
 arch/mips/boot/dts/realtek/cisco_sg220-26.dts | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/arch/mips/boot/dts/realtek/cisco_sg220-26.dts b/arch/mips/boot/dts/realtek/cisco_sg220-26.dts
index cb85d172a1d3..fab3d552404d 100644
--- a/arch/mips/boot/dts/realtek/cisco_sg220-26.dts
+++ b/arch/mips/boot/dts/realtek/cisco_sg220-26.dts
@@ -4,6 +4,8 @@
 
 #include "rtl838x.dtsi"
 
+#include <dt-bindings/gpio/gpio.h>
+
 / {
 	model = "Cisco SG220-26";
 	compatible = "cisco,sg220-26", "realtek,rtl8382-soc";
@@ -17,6 +19,13 @@ memory@0 {
 		device_type = "memory";
 		reg = <0x0 0x8000000>;
 	};
+
+	gpio-restart {
+		compatible = "gpio-restart";
+		gpios = <&gpio0 1 GPIO_ACTIVE_LOW>;
+		priority = <192>;
+		open-source;
+	};
 };
 
 &uart0 {
-- 
2.48.1


  parent reply	other threads:[~2025-01-19 18:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 18:34 [PATCH 0/9] mips: dts: Split Realtek devicetrees Sander Vanheule
2025-01-19 18:34 ` [PATCH 1/9] mips: dts: realtek: Decouple RTL930x base DTSI Sander Vanheule
2025-01-20  1:20   ` Chris Packham
2025-01-19 18:34 ` [PATCH 2/9] mips: dts: realtek: Clean up CPU clocks Sander Vanheule
2025-01-20  1:21   ` Chris Packham
2025-01-19 18:34 ` [PATCH 3/9] mips: dts: realtek: Add address to SoC node name Sander Vanheule
2025-01-20  1:22   ` Chris Packham
2025-01-19 18:34 ` [PATCH 4/9] mips: dts: realtek: Fold rtl83xx into rtl838x Sander Vanheule
2025-01-20  1:23   ` Chris Packham
2025-01-19 18:34 ` [PATCH 5/9] mips: dts: realtek: Add SoC IRQ node for RTL838x Sander Vanheule
2025-01-19 18:34 ` [PATCH 6/9] mips: dts: realtek: Correct uart interrupt-parent Sander Vanheule
2025-01-19 18:34 ` [PATCH 7/9] mips: dts: realtek: Replace uart clock property Sander Vanheule
2025-01-19 18:34 ` [PATCH 8/9] mips: dts: realtek: Add RTL838x SoC peripherals Sander Vanheule
2025-01-19 18:34 ` Sander Vanheule [this message]
2025-02-21 15:27 ` [PATCH 0/9] mips: dts: Split Realtek devicetrees Thomas Bogendoerfer
2025-02-22 10:57   ` Sander Vanheule

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=20250119183424.259353-10-sander@svanheule.net \
    --to=sander@svanheule.net \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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