From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v3 5/5] dt-bindings: watchdog: renesas,wdt: add SWDT exception for V3H
Date: Tue, 7 Oct 2025 17:20:10 +0200 [thread overview]
Message-ID: <20251007152007.14508-12-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20251007152007.14508-7-wsa+renesas@sang-engineering.com>
Normally, RWDT and SWDT can share the same binding. But on R-Car V3H,
SWDT misses the reset bit. Add this exception.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
Changes since v2:
* new patch
.../devicetree/bindings/watchdog/renesas,wdt.yaml | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml b/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
index 08ba128bf442..727f034e7f92 100644
--- a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
+++ b/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
@@ -39,6 +39,7 @@ properties:
- renesas,r8a77965-wdt # R-Car M3-N
- renesas,r8a77970-wdt # R-Car V3M
- renesas,r8a77980-wdt # R-Car V3H
+ - renesas,r8a77980-swdt # R-Car V3H SWDT (no reset)
- renesas,r8a77990-wdt # R-Car E3
- renesas,r8a77995-wdt # R-Car D3
- const: renesas,rcar-gen3-wdt # R-Car Gen3 and RZ/G2
@@ -74,11 +75,22 @@ required:
- clocks
- interrupts
- power-domains
- - resets
allOf:
- $ref: watchdog.yaml#
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: renesas,r8a77980-swdt
+ then:
+ properties:
+ resets: false
+ else:
+ required:
+ - resets
+
additionalProperties: false
examples:
--
2.47.2
next prev parent reply other threads:[~2025-10-07 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 15:20 [PATCH v3 0/5] dt-bindings: watchdog: factor out RZ watchdogs Wolfram Sang
2025-10-07 15:20 ` [PATCH v3 1/5] dt-bindings: watchdog: factor out RZ/A watchdog Wolfram Sang
2025-10-08 10:04 ` Geert Uytterhoeven
2025-10-07 15:20 ` [PATCH v3 2/5] dt-bindings: watchdog: factor out RZ/N1 watchdog Wolfram Sang
2025-10-08 10:19 ` Geert Uytterhoeven
2025-10-07 15:20 ` [PATCH v3 3/5] dt-bindings: watchdog: factor out RZ/G2L watchdog Wolfram Sang
2025-10-08 10:25 ` Geert Uytterhoeven
2025-10-07 15:20 ` [PATCH v3 4/5] dt-bindings: watchdog: factor out RZ/V2H(P) watchdog Wolfram Sang
2025-10-08 10:36 ` Geert Uytterhoeven
2025-10-07 15:20 ` Wolfram Sang [this message]
2025-10-08 10:45 ` [PATCH v3 5/5] dt-bindings: watchdog: renesas,wdt: add SWDT exception for V3H Geert Uytterhoeven
2025-10-08 13:40 ` Wolfram Sang
2025-10-08 13:17 ` [PATCH v3 0/5] dt-bindings: watchdog: factor out RZ watchdogs Rob Herring
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=20251007152007.14508-12-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.org \
/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).