From: Sander Vanheule <sander@svanheule.net>
To: Rustam Adilov <adilov@disroot.org>
Cc: Rob Herring <robh@kernel.org>,
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>,
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: Fri, 15 May 2026 22:42:26 +0200 [thread overview]
Message-ID: <e73cb768716085a8bc461262ad8108e33ac97981.camel@svanheule.net> (raw)
In-Reply-To: <d73e53888ab7d8541c5d84e733c04166@disroot.org>
On Fri, 2026-05-15 at 19:14 +0000, Rustam Adilov wrote:
> Hello Sander,
> On 2026-05-15 08:47, Sander Vanheule wrote:
> > Rustam, will you take it from here to add the two-part compatible for the
> > RTL9706C? Since you won't need update the driver, I guess a single patch
> > would
> > do.
>
> I can for sure, but would you mind clarifying what needs to be done?
> From my understanding two-part compatible for RTL9607C would look like
> compatible = "realtek,rtl9607-wdt", "realtek,rtl8380-wdt";
As I understand from the maintainers, this is indeed the desired approach.
> But it's only gonna be relevant to OpenWrt for now.
> Do i need to patch the realtek,otto-wdt.yaml file in the same way as
> your patch 1 here?
Yes, you'll need to make a distinction between the new two-part compatible,
while still allowing the old one-part compatible (which then should not be
deprecated). Another binding that implements this is fsl-imx7ulp-wdt.yaml, so
you can also use that style, if you prefer.
Best,
Sander
prev parent reply other threads:[~2026-05-15 20:42 UTC|newest]
Thread overview: 12+ 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 ` [PATCH v2 0/2] " Rob Herring
2026-05-14 16:25 ` Sander Vanheule
2026-05-14 20:57 ` Rob Herring
2026-05-15 8:47 ` Sander Vanheule
2026-05-15 19:14 ` Rustam Adilov
2026-05-15 20:42 ` Sander Vanheule [this message]
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=e73cb768716085a8bc461262ad8108e33ac97981.camel@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