Linux Watchdog driver development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yureka Lilian" <yureka@cyberchaos.dev>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 05/10] dt-bindings: power: apple,pmgr-pwrstate: Add t8132 compatible
Date: Sun, 05 Jul 2026 13:25:42 +0000	[thread overview]
Message-ID: <20260705132543.373C01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260705-apple-m4-initial-devicetrees-v1-5-e5655ee56523@cyberchaos.dev>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The new compatible string 'apple,t8132-aic3' was not added to the conditional block enforcing '#interrupt-cells'.
--

commit 4be0e67c14a594eec020638f7ba5290c4bf05496
Author: Yureka Lilian <yureka@cyberchaos.dev>

dt-bindings: interrupt-controller: apple,aic2: Add apple,t8132 compatible
    
The Apple t8132 (M4) SoC uses an AIC3 as interrupt controller, same as
the M3 predecessor.

> diff --git a/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml b/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
> index d0d9a90e96e7b..7171c8c09feaf 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
> @@ -44,6 +44,7 @@ properties:
>        - items:
>            - enum:
>                - apple,t6030-aic3
> +              - apple,t8132-aic3

[Severity: Low]
This isn't a bug, but should the 'apple,t8132-aic3' compatible string be added
to the conditional block enforcing the '#interrupt-cells' constraint?

Looking at the allOf if-then block further down in the file:

allOf:
  - $ref: /schemas/interrupt-controller.yaml#
  - if:
      properties:
        compatible:
          contains:
            enum:
              - apple,t8112-aic
              - apple,t8122-aic3

This conditional block enumerates the prior generations (t8112-aic, t8122-aic3)
but is missing the newly added t8132-aic3 compatible string.

While dt-validate may still enforce the constraint via the mandatory
'apple,t8122-aic3' fallback string matching in the contains clause, omitting
the new generation string from the enumeration directly violates the subsystem
rules for generating consistent schema checks.

>            - const: apple,t8122-aic3
>        - const: apple,t8122-aic3
>

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260705-apple-m4-initial-devicetrees-v1-0-e5655ee56523@cyberchaos.dev?part=5

  reply	other threads:[~2026-07-05 13:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 13:17 [PATCH 00/10] Initial Apple silicon M4 device trees and dt-bindings Yureka Lilian
2026-07-05 13:17 ` [PATCH 01/10] dt-bindings: arm: cpus: Add Apple M4 CPU core compatibles Yureka Lilian
2026-07-05 13:17 ` [PATCH 02/10] dt-bindings: interrupt-controller: apple,aic2: Add apple,t8132 compatible Yureka Lilian
2026-07-05 13:24   ` sashiko-bot
2026-07-05 13:36     ` Yureka Lilian
2026-07-05 13:17 ` [PATCH 03/10] dt-bindings: watchdog: apple,wdt: Add t8132 compatible Yureka Lilian
2026-07-05 13:17 ` [PATCH 04/10] dt-bindings: arm: apple: apple,pmgr: " Yureka Lilian
2026-07-05 13:27   ` sashiko-bot
2026-07-05 13:17 ` [PATCH 05/10] dt-bindings: power: apple,pmgr-pwrstate: " Yureka Lilian
2026-07-05 13:25   ` sashiko-bot [this message]
2026-07-05 13:17 ` [PATCH 06/10] dt-bindings: pinctrl: apple,pinctrl: " Yureka Lilian
2026-07-05 13:17 ` [PATCH 07/10] dt-bindings: i2c: apple,i2c: " Yureka Lilian
2026-07-05 13:25   ` sashiko-bot
2026-07-05 13:17 ` [PATCH 08/10] dt-bindings: pwm: apple,s5l-fpwm: " Yureka Lilian
2026-07-05 13:17 ` [PATCH 09/10] dt-bindings: arm: apple: Add M4 based devices Yureka Lilian
2026-07-05 13:28   ` sashiko-bot
2026-07-05 13:37     ` Yureka Lilian
2026-07-05 13:17 ` [PATCH 10/10] arm64: dts: apple: Add minimal t8132 (M4) device trees Yureka Lilian
2026-07-05 13:28   ` sashiko-bot
2026-07-05 13:44     ` Yureka Lilian

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=20260705132543.373C01F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=yureka@cyberchaos.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