Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Rustam Adilov <adilov@disroot.org>
Cc: Sander Vanheule <sander@svanheule.net>,
	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>,
	linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: watchdog: realtek,otto-wdt: add compatible for RTL9607C
Date: Mon, 11 May 2026 16:52:29 +0100	[thread overview]
Message-ID: <20260511-alienate-guidable-d503194e6a93@spud> (raw)
In-Reply-To: <94a75930847c2b7a221736c41a1da67d@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]

On Sun, May 10, 2026 at 08:19:09AM +0000, Rustam Adilov wrote:
> Hello,
> On 2026-05-09 18:13, Conor Dooley wrote:
> > On Sat, May 09, 2026 at 09:31:00PM +0500, Rustam Adilov wrote:
> >> Add the realtek,rtl9607-wdt compatible to the Realtek Otto watchdog
> >> binding.
> >> 
> >> Signed-off-by: Rustam Adilov <adilov@disroot.org>
> >> ---
> >>  Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml | 1 +
> >>  1 file changed, 1 insertion(+)
> >> 
> >> diff --git a/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml b/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml
> >> index 1f5390a67cdb..ac9db40b12dc 100644
> >> --- a/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml
> >> +++ b/Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml
> >> @@ -30,6 +30,7 @@ properties:
> >>        - realtek,rtl8390-wdt
> >>        - realtek,rtl9300-wdt
> >>        - realtek,rtl9310-wdt
> >> +      - realtek,rtl9607-wdt
> > 
> > Please explain in your commit message why this new device is not
> > compatible with the existing ones, particularly given the driver patch
> > implies that it would be.
> > pw-bot: changes-requested
> 
> Is the fact "RTL9607C is different SoC compared to the others in the list" not
> enough of a reason to include even though the all of them have an identical watchdog
> timer device? But yes, i can use any other compatible just as fine.

No. And to be clear, I'm not asking you to use one of the other
compatibles. I'm asking you to use one of the existing ones as a
fallback.

> Maybe its just difference in maintainers because the RTL9310 [1] was accepted and
> had the identical case to this one.
> 
> [1]- https://lore.kernel.org/linux-watchdog/84d873d7dd375cd2392f89fa6bd9e0fe5dda4e1c.1656356377.git.sander@svanheule.net/

Probably the same feedback should have been provided there.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-11 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09 16:30 [PATCH 0/3] watchdog: realtek-otto: Make use of regmap API and add RTL9607C support Rustam Adilov
2026-05-09 16:30 ` [PATCH 1/3] watchdog: realtek-otto: Change to use regmap API Rustam Adilov
2026-05-09 17:16   ` sashiko-bot
2026-05-09 16:31 ` [PATCH 2/3] dt-bindings: watchdog: realtek,otto-wdt: add compatible for RTL9607C Rustam Adilov
2026-05-09 18:13   ` Conor Dooley
2026-05-10  8:19     ` Rustam Adilov
2026-05-11 15:52       ` Conor Dooley [this message]
2026-05-10 19:23     ` Sander Vanheule
2026-05-09 16:31 ` [PATCH 3/3] watchdog: realtek-otto: add RTL9607C support Rustam Adilov
2026-05-09 17:27   ` sashiko-bot
2026-05-10 18:12     ` Sander Vanheule
2026-05-10 15:13 ` [PATCH 0/3] watchdog: realtek-otto: Make use of regmap API and " Guenter Roeck

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=20260511-alienate-guidable-d503194e6a93@spud \
    --to=conor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox