Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alexandru Chimac" <alex@chimac.ro>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: samsung: Require clocks for Exynos9610 pinctrl nodes
Date: Tue, 22 Sep 2026 12:33:18 +0000	[thread overview]
Message-ID: <20260922123319.1E52B1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922-exynos9610-pinctrl-patch-v1-1-26d8108c1802@chimac.ro>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: pinctrl: over-constraint on exynos9610 clocks
--

commit 16b59636da37f1324cb6823b4e5fa7ff00df75fb
Author: Alexandru Chimac <alex@chimac.ro>
Subject: dt-bindings: pinctrl: samsung: Require clocks for Exynos9610 pinctrl nodes

This commit modifies the Samsung pinctrl devicetree binding to require
clocks for Exynos9610 pin controllers. It adds the Exynos9610 compatible
string to an existing conditional block that mandates clock properties.

> diff --git a/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml
> index 1feb6a6fc6908..e4fdedb29631b 100644
> --- a/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml
> @@ -140,6 +140,7 @@ allOf:
>              enum:
>                - google,gs101-pinctrl
>                - samsung,exynos8890-pinctrl
> +              - samsung,exynos9610-pinctrl
>      then:
>        required:
>          - clocks

[Severity: Low]
Will this cause schema validation errors for the PINCTRL_TOP node?

The commit message notes that PINCTRL_TOP does not have a clock, but adding
the compatible string to this allOf if-then conditional block enforces that
all Exynos9610 pinctrl nodes must have the clocks and clock-names properties.

Since all pin controller blocks on this SoC (including TOP) share the same
samsung,exynos9610-pinctrl compatible string, this seems to over-constrain
the binding and would cause dtbs_check to fail for PINCTRL_TOP. 

Should samsung,exynos9610-pinctrl instead be exempted from the else block
(which sets clocks: false) without moving it into this then block where
clocks are strictly required?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260922-exynos9610-pinctrl-patch-v1-1-26d8108c1802@chimac.ro?part=1

  reply	other threads:[~2026-09-22 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 12:07 [PATCH] dt-bindings: pinctrl: samsung: Require clocks for Exynos9610 pinctrl nodes Alexandru Chimac
2026-09-22 12:33 ` sashiko-bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-22 12:15 Alexandru Chimac
2026-09-22 12:31 ` sashiko-bot
2026-09-22 14:24   ` Alexandru Chimac
2026-09-22 14:25 ` Alexandru Chimac
2026-09-23 14:58 ` Krzysztof Kozlowski
2026-09-23 16:14   ` Alexandru Chimac
2026-09-28  8:06     ` Krzysztof Kozlowski

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=20260922123319.1E52B1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alex@chimac.ro \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@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