From: Rob Herring <robh@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Sander Vanheule <sander@svanheule.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
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 1/2] dt-bindings: watchdog: realtek,otto-wdt: Add fallback compatible
Date: Thu, 14 May 2026 11:03:52 -0500 [thread overview]
Message-ID: <20260514160352.GA841147-robh@kernel.org> (raw)
In-Reply-To: <1be8c11b-a020-44d6-86ef-109418e1d968@roeck-us.net>
On Wed, May 13, 2026 at 05:20:59PM -0700, Guenter Roeck wrote:
> On Tue, May 12, 2026 at 10:48:53PM +0200, Sander Vanheule wrote:
> > As all known hardware instantiations of this watchdog behave the same, a
> > fallback compatible can be added.
> >
> > To remain compatible with existing single-compatible bindings, the
> > current compatibles are duplicated. New compatibles should only be added
> > to the list with fallback.
> >
> > Signed-off-by: Sander Vanheule <sander@svanheule.net>
> > ---
> > Changes since v1:
> > - Fix indendations
> > - Add deprecated property to old compatible
> > - Use two-part compatible in example
> > ---
> > .../bindings/watchdog/realtek,otto-wdt.yaml | 22 ++++++++++++++-----
> > 1 file changed, 16 insertions(+), 6 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml b/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml
> > index 1f5390a67cdb..e470e0fcbb2a 100644
> > --- a/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml
> > +++ b/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml
> > @@ -25,11 +25,21 @@ allOf:
> >
> > properties:
> > compatible:
> > - enum:
> > - - realtek,rtl8380-wdt
> > - - realtek,rtl8390-wdt
> > - - realtek,rtl9300-wdt
> > - - realtek,rtl9310-wdt
> > + oneOf:
> > + - items:
> > + - enum:
> > + - realtek,rtl8380-wdt
> > + - realtek,rtl8390-wdt
> > + - realtek,rtl9300-wdt
> > + - realtek,rtl9310-wdt
> > + - const: realtek,otto-wdt
>
> For the Apple watchdog driver, the generic property "apple,wdt" is
> considered to be bad and is not supposed to be used for newer chips.
> For this watchdog driver, a generic property is introduced.
>
> What is the overall logic ? Is there some rule when a generic property
> such as "realtek,otto-wdt" is appropriate and preferred, and when it isn't
> (as in "apple,wdt") ?
Never preferred. Retroactively adding them, that's a definite no.
Rob
next prev parent reply other threads:[~2026-05-14 16:03 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 [this message]
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 ` [PATCH v2 0/2] " Rob Herring
2026-05-14 16:25 ` 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=20260514160352.GA841147-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