Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yassine Oudjana" <yassine.oudjana@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 3/6] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Add MT6795
Date: Sat, 30 May 2026 15:17:17 +0000	[thread overview]
Message-ID: <20260530151718.345A61F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260530145800.1029920-4-y.oudjana@protonmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The global `maxItems: 1` constraint on the `interrupts` property prevents the `mediatek,mt6795-pinctrl` compatible from specifying its two supported hardware interrupts.
--

commit 21e9f5d9b0c26d0a8f4207afe5723d54c0b4b7e6
Author: Yassine Oudjana <y.oudjana@protonmail.com>

dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Add MT6795

This commit combines the MT6795 pin controller document into the MT6779
binding. It uses conditionals to define valid values for properties like
interrupts and drive-strength for each hardware variant.

> diff --git a/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml
> index 4dc9504e24ad5..2124804c88631 100644
> --- a/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml

[ ... ]

> @@ -81,6 +83,45 @@ allOf:
>              - const: iocfg_lt
>              - const: iocfg_tl
>              - const: eint

[ ... ]

> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: mediatek,mt6795-pinctrl
> +    then:
> +      properties:
> +        reg:
> +          minItems: 2
> +          maxItems: 2
> +
> +        reg-names:
> +          items:
> +            - const: base
> +            - const: eint
> +
> +        interrupts:
> +          minItems: 1
> +          items:
> +            - description: EINT interrupt
> +            - description: EINT event_b interrupt

[Severity: Medium]
Will this conditional block fail schema validation due to the global interrupts
definition?

The top-level interrupts property in this file enforces a global maxItems: 1
limit for all compatibles:

properties:
  interrupts:
    maxItems: 1
    description: ...

Because JSON schema constraints are additive, allowing two items here for
mediatek,mt6795-pinctrl won't override the global maxItems: 1 limit. This
causes device trees like mt6795.dtsi (which specifies two interrupts
for pio: pinctrl@10005000) to fail validation. Should the global maximum
limit be relaxed to maxItems: 2 so this variant can use both interrupts?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260530145800.1029920-1-y.oudjana@protonmail.com?part=3

  reply	other threads:[~2026-05-30 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 14:57 [PATCH v8 0/6] MediaTek pinctrl DT binding cleanup and MT6735 pinctrl support Yassine Oudjana
2026-05-30 14:57 ` [PATCH v8 1/6] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Pull pinctrl node changes from MT6795 document Yassine Oudjana
2026-05-30 14:57 ` [PATCH v8 2/6] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Improve pinctrl subnode and property descriptions Yassine Oudjana
2026-05-30 15:09   ` sashiko-bot
2026-05-30 14:57 ` [PATCH v8 3/6] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Add MT6795 Yassine Oudjana
2026-05-30 15:17   ` sashiko-bot [this message]
2026-05-30 14:57 ` [PATCH v8 4/6] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Document MT6765 pin controller Yassine Oudjana
2026-05-30 15:29   ` sashiko-bot
2026-05-30 14:57 ` [PATCH v8 5/6] dt-bindings: pinctrl: mediatek: Add bindings for MT6735 " Yassine Oudjana
2026-05-30 15:35   ` sashiko-bot
2026-05-30 14:57 ` [PATCH v8 6/6] pinctrl: mediatek: Add MT6735 pinctrl driver Yassine Oudjana
2026-05-30 15:55   ` 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=20260530151718.345A61F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=yassine.oudjana@gmail.com \
    /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