From: Sander Vanheule <sander@svanheule.net>
To: 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>
Cc: Rustam Adilov <adilov@disroot.org>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sander Vanheule <sander@svanheule.net>
Subject: [PATCH 0/2] watchdog: realtek-otto: add fallback compatible
Date: Tue, 12 May 2026 13:08:46 +0200 [thread overview]
Message-ID: <20260512110848.106620-1-sander@svanheule.net> (raw)
Like for the GPIO hardware of the Realtek Otto platform, add a fallback
compatible for the watchdog hardware.
For backward compatibility, the binding will still allow current
single-compatible devicetrees to work, but new devicetrees, including
new compatibles, should use a two-component compatible.
This series serves to address comments regarding the device compatibles
for the patches adding RTL9607C watchdog support [1].
[1] https://lore.kernel.org/lkml/20260509163101.722793-1-adilov@disroot.org/
Sander Vanheule (2):
dt-bindings: watchdog: realtek,otto-wdt: Add fallback compatible
watchdog: realtek-otto: add fallback compatible
.../bindings/watchdog/realtek,otto-wdt.yaml | 19 ++++++++++++++-----
drivers/watchdog/realtek_otto_wdt.c | 2 ++
2 files changed, 16 insertions(+), 5 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-12 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 11:08 Sander Vanheule [this message]
2026-05-12 11:08 ` [PATCH 1/2] dt-bindings: watchdog: realtek,otto-wdt: Add fallback compatible Sander Vanheule
2026-05-12 12:43 ` Rob Herring (Arm)
2026-05-12 11:08 ` [PATCH 2/2] watchdog: realtek-otto: add " 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=20260512110848.106620-1-sander@svanheule.net \
--to=sander@svanheule.net \
--cc=adilov@disroot.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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