From: Rob Herring <robh@kernel.org>
To: Sander Vanheule <sander@svanheule.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rustam Adilov <adilov@disroot.org>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] watchdog: realtek-otto: add fallback compatible
Date: Thu, 14 May 2026 11:10:08 -0500 [thread overview]
Message-ID: <20260514161008.GB841147-robh@kernel.org> (raw)
In-Reply-To: <20260512204854.8931-1-sander@svanheule.net>
On Tue, May 12, 2026 at 10:48:52PM +0200, Sander Vanheule wrote:
> 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/
You misunderstood the discussion (though some came after this). The
fallback should be one of the existing compatibles (the oldest one), so
there are no driver changes needed for the OS. Creating a new fallback
completely misses that point.
Rob
next prev parent reply other threads:[~2026-05-14 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 20:48 [PATCH v2 0/2] watchdog: realtek-otto: add fallback compatible Sander Vanheule
2026-05-12 20:48 ` [PATCH v2 1/2] dt-bindings: watchdog: realtek,otto-wdt: Add " Sander Vanheule
2026-05-14 0:20 ` Guenter Roeck
2026-05-14 16:03 ` Rob Herring
2026-05-14 16:08 ` Krzysztof Kozlowski
2026-05-12 20:48 ` [PATCH v2 2/2] watchdog: realtek-otto: add " Sander Vanheule
2026-05-14 16:10 ` Rob Herring [this message]
2026-05-14 16:25 ` [PATCH v2 0/2] " Sander Vanheule
2026-05-14 20:57 ` 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=20260514161008.GB841147-robh@kernel.org \
--to=robh@kernel.org \
--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=sander@svanheule.net \
--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