From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sander Vanheule <sander@svanheule.net>, Rob Herring <robh@kernel.org>
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: Sat, 16 May 2026 11:16:28 +0200 [thread overview]
Message-ID: <86434197-1338-4fc3-a0f2-e9ecb464f7e2@kernel.org> (raw)
In-Reply-To: <9f81a947b65cafd44b293e05080b1fd2820cea06.camel@svanheule.net>
On 14/05/2026 18:25, Sander Vanheule wrote:
> I also think "apple,wdt" is a bad example to compare with "realtek,otto-wdt".
> The former only specifies the vendor, while the latter refers to the line of
> SoCs this IP block is used for. Although I see the docs also discourage family
> compatibles.
>
> If I may ask, what is the rationale for preferring the "older implementation"
> approach over a "family compatible" to match the common subset of supported
> features?
To add on top of Rob's:
There were already a few cases of generic fallbacks of a few IP blocks
in Qualcomm SoC, which were true for like a few years (50-100 different
SoCs!). So you really thought a generic compatible is generic, matching
entire family or all SoCS.
And then last year they came with a few new ones which are NOT
COMPATIBLE with that generic one.
So let's create another generic fallback? But how do you define it? What
is the generic part there? Even within family you have differences and
in many cases SW people just don't know.
IMO, the generic fallback is fake construct or rather "faith" construct:
I hope these devices will be compatible enough to use that generic
fallback. Hope is not enough and if that's the only thing you got, then
just use specific fallback.
And that's exactly the feedback Qualcomm got for these new "generic"
variants.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-05-16 9:16 UTC|newest]
Thread overview: 13+ 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
2026-05-16 9:16 ` Krzysztof Kozlowski [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=86434197-1338-4fc3-a0f2-e9ecb464f7e2@kernel.org \
--to=krzk@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=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.