From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: sashiko-reviews@lists.linux.dev,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
conor+dt@kernel.org, devicetree@vger.kernel.org,
wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v3 1/3] dt-bindings: mfd: syscon: Disallow simple-bus with syscon
Date: Tue, 9 Jun 2026 12:52:59 -0500 [thread overview]
Message-ID: <20260609175259.GA2210649-robh@kernel.org> (raw)
In-Reply-To: <20260609-appraiser-sedate-c76c7b06690c@spud>
On Tue, Jun 09, 2026 at 05:36:30PM +0100, Conor Dooley wrote:
> On Mon, Jun 08, 2026 at 08:54:05PM +0000, sashiko-bot@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > - [Medium] The patch introduces several new compatible strings (e.g., `ti,am3352-scm-conf`) to the exception list without documenting them in any valid dt-binding schema. This causes a bisectability breakage in `dtbs_check` during the series and leaves permanent 'undocumented compatible' warnings at the end of the series.
> > --
> >
> > commit 0cddec624a3b6ba2f0c447b95621f32101d2e31f
> > Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> >
> > dt-bindings: mfd: syscon: Disallow simple-bus with syscon
> >
> > This commit adds a schema to disallow the combination of syscon and
> > simple-bus compatibles. It includes an exception list for legacy
> > configurations that currently rely on this pattern.
> >
> > > diff --git a/Documentation/devicetree/bindings/mfd/syscon-common.yaml b/Documentation/devicetree/bindings/mfd/syscon-common.yaml
> > > index 14a08e7bc8bdd..2d5eef5add544 100644
> > > --- a/Documentation/devicetree/bindings/mfd/syscon-common.yaml
> > > +++ b/Documentation/devicetree/bindings/mfd/syscon-common.yaml
> > [ ... ]
> > > @@ -52,11 +53,44 @@ allOf:
> > > contains:
> > > const: simple-mfd
> > > then:
> > > + # Always require a specific compatible for syscon with simple-mfd
> > > properties:
> > > compatible:
> > > minItems: 3
> > > maxItems: 5
> > >
> > > + - if:
> > > + properties:
> > > + compatible:
> > > + contains:
> > > + const: simple-bus
> > > + then:
> > > + # simple-bus conflicts with syscon - if a device is a system controller
> > > + # with miscellaneous registers, then it has at least one dedicated
> > > + # function thus it is not a simple bus. Allow existing exceptions.
> > > + if:
> > > + properties:
> > > + compatible:
> > > + not:
> > > + contains:
> > > + # This list CANNOT grow
> >
> > [Severity: Medium]
> > Will this break bisectability for dtbs_check? Since the DTS files are
> > updated later in the series, it seems like existing TI DTS files using syscon
> > and simple-bus without these new specific compatibles will fail validation
> > when this patch is applied.
>
> Perhaps worth telling the sashiko people that transitory warnings like
> this aren't something we care about, especially since even the normal
> development process for devicetrees introduces validation issues in the
> platform maintainer branches.
I think that is on us to tweak the review prompts. There's already one
for DT that none of us wrote. Though really I don't think that's all
that maintainable. Really, IMO sashiko itself should be able to
incorporate feedback like any other reviewer/developer.
Rob
next prev parent reply other threads:[~2026-06-09 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 20:44 [PATCH v3 0/3] dt-bindings: mfd: syscon: Tighten checks Krzysztof Kozlowski
2026-06-08 20:44 ` [PATCH v3 1/3] dt-bindings: mfd: syscon: Disallow simple-bus with syscon Krzysztof Kozlowski
2026-06-08 20:54 ` sashiko-bot
2026-06-09 16:36 ` Conor Dooley
2026-06-09 17:52 ` Rob Herring [this message]
2026-06-08 20:44 ` [PATCH v3 2/3] dt-bindings: mfd: syscon: Drop custom select for older dtschema Krzysztof Kozlowski
2026-06-09 16:28 ` Conor Dooley
2026-06-08 20:44 ` [PATCH v3 3/3] ARM: dts: ti: Add specific compatibles for SCM conf nodes Krzysztof Kozlowski
2026-06-08 20:56 ` sashiko-bot
2026-06-09 16:34 ` Conor Dooley
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=20260609175259.GA2210649-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.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