From: Alexandru Chimac <alex@chimac.ro>
To: sashiko-reviews@lists.linux.dev, sashiko-bot@kernel.org
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: samsung: Require clocks for Exynos9610 pinctrl nodes
Date: Tue, 22 Sep 2026 17:24:20 +0300 (EEST) [thread overview]
Message-ID: <1591117350.78120.1790087060934@app.mailbox.org> (raw)
In-Reply-To: <20260922123157.927751F000FF@smtp.kernel.org>
Hello!
> On 09/22/2026 3:31 PM EEST sashiko-bot@kernel.org wrote:
>
>
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] dt-bindings: unconditional clock requirement breaks PINCTRL_TOP node
> --
>
> commit 8b1ed6a89af0afe8c1009cac2d735ea6bee6ec4b
> Author: Alexandru Chimac <alex@chimac.ro>
>
> dt-bindings: pinctrl: samsung: Require clocks for Exynos9610 pinctrl nodes
>
> This commit updates the Samsung pinctrl bindings to require clocks for nodes
> using the Exynos9610 compatible string, as most of these controllers have
> designated clocks.
>
> > 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: Medium]
> Will this unconditional requirement break schema validation for the clockless
> PINCTRL_TOP node?
On TOP pinctrl node we can just set "clocks = <0>;", but that is a bit of
a hack.
>
> The commit message explicitly acknowledges that the PINCTRL_TOP node does not
> have clocks. Since all Exynos9610 pin controllers share the same compatible
> string, applying an unconditional required rule for clocks causes a structurally
> correct PINCTRL_TOP device tree node to fail dtbs_check validation.
>
> Could the schema be adjusted so that clocks are allowed but not universally
> required for this compatible string?
To be honest, I've tried looking a bit into the bindings format
and I haven't found a way of doing an "else if" in this conditional. If
there is a way to add an "else if" to this, I will send a revised patch.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260922-exynos9610-pinctrl-patch-v1-1-f6d816696591@chimac.ro?part=1
Regards,
Alexandru Chimac
next prev parent reply other threads:[~2026-09-22 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 12:15 [PATCH] dt-bindings: pinctrl: samsung: Require clocks for Exynos9610 pinctrl nodes Alexandru Chimac
2026-09-22 12:31 ` sashiko-bot
2026-09-22 14:24 ` Alexandru Chimac [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2026-09-22 12:07 Alexandru Chimac
2026-09-22 12:33 ` 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=1591117350.78120.1790087060934@app.mailbox.org \
--to=alex@chimac.ro \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-bot@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