Linux Watchdog driver development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Janne Grunau" <j@jannau.net>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 3/6] dt-bindings: watchdog: apple,wdt: Add t8122 compatible
Date: Tue, 05 May 2026 11:35:39 +0000	[thread overview]
Message-ID: <20260505113539.DD2D6C2BCB4@smtp.kernel.org> (raw)
In-Reply-To: <20260505-apple-m3-initial-devicetrees-v2-3-b0c2f3519e0e@jannau.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The newly added `apple,t8122-wdt` compatible string will not bind to the watchdog driver because the driver does not match `apple,t8103-wdt` and the schema prevents including the generic `apple,wdt` fallback.
--

commit c2fb9f5326f211450e3923c7641f1f6384822f86
Author: Janne Grunau <j@jannau.net>

dt-bindings: watchdog: apple,wdt: Add t8122 compatible

This commit adds the apple,t8122-wdt compatible string to the apple,wdt
device tree binding. It is added to the branch that restricts the fallback
to apple,t8103-wdt.

> diff --git a/Documentation/devicetree/bindings/watchdog/apple,wdt.yaml b/Documentation/devicetree/bindings/watchdog/apple,wdt.yaml
> index 05602678c070d..845b5e8b5abc3 100644
> --- a/Documentation/devicetree/bindings/watchdog/apple,wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/apple,wdt.yaml
> @@ -16,7 +16,9 @@ properties:
>    compatible:
>      oneOf:
>        - items:
> -          - const: apple,t6020-wdt
> +          - enum:
> +              - apple,t6020-wdt
> +              - apple,t8122-wdt
>            - const: apple,t8103-wdt

Will this prevent the driver from probing on t8122 devices?

This schema requires exactly two compatible strings: apple,t8122-wdt
followed by apple,t8103-wdt. This exact match requirement prevents the
inclusion of the generic apple,wdt fallback string.

Looking at drivers/watchdog/apple_wdt.c, the driver's of_match_table only
matches { .compatible = "apple,wdt" } and does not match apple,t8103-wdt.

If a device tree conforms to this schema by omitting the generic fallback,
does it cause a regression where the driver silently fails to bind?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260505-apple-m3-initial-devicetrees-v2-0-b0c2f3519e0e@jannau.net?part=3

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 11:02 [PATCH v2 0/6] Initial Apple silicon M3 device trees and dt-bindings Janne Grunau
2026-05-05 11:02 ` [PATCH v2 1/6] dt-bindings: arm: apple: apple,pmgr: Add t8122 compatible Janne Grunau
2026-05-05 11:02 ` [PATCH v2 2/6] dt-bindings: power: apple,pmgr-pwrstate: " Janne Grunau
2026-05-05 11:02 ` [PATCH v2 3/6] dt-bindings: watchdog: apple,wdt: " Janne Grunau
2026-05-05 11:35   ` sashiko-bot [this message]
2026-05-05 13:17   ` Guenter Roeck
2026-05-05 11:02 ` [PATCH v2 4/6] dt-bindings: pwm: apple,s5l-fpwm: " Janne Grunau
2026-05-05 11:02 ` [PATCH v2 5/6] dt-bindings: arm: apple: Add M3 based devices Janne Grunau
2026-05-05 11:02 ` [PATCH v2 6/6] arm64: dts: apple: Initial t8122 (M3) device trees Janne Grunau
2026-05-05 12:27   ` sashiko-bot

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=20260505113539.DD2D6C2BCB4@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=j@jannau.net \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=sashiko@lists.linux.dev \
    /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