From: sashiko-bot@kernel.org
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Cc: conor+dt@kernel.org, wsa+renesas@sang-engineering.com,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: mfd: syscon: Disallow simple-bus with syscon
Date: Mon, 08 Jun 2026 14:06:50 +0000 [thread overview]
Message-ID: <20260608140650.CF8DE1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260608-n-dt-bindings-simple-bus-syscon-v2-1-0203e6c249dc@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] DT Binding Violation: Undocumented Compatibles and Validation Breakage
--
commit 73d2cc9a54e99039c48884fc1ade73467dc1c67d
Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
dt-bindings: mfd: syscon: Disallow simple-bus with syscon
This commit adds a schema rule to disallow the combination of syscon and
simple-bus compatibles. It creates exceptions for existing upstream device
trees that already use this pattern. It also introduces new compatibles for
several TI platforms to bypass this restriction without a dedicated schema.
> diff --git a/Documentation/devicetree/bindings/mfd/syscon-common.yaml b/Documentation/devicetree/bindings/mfd/syscon-common.yaml
> index 14a08e7bc8bdd..315357da146ea 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon-common.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon-common.yaml
> @@ -57,6 +57,38 @@ allOf:
> 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
> + enum:
> + - cznic,turris1x-cpld
> + - img,pistachio-cr-periph
> + - ti,am3352-scm-conf
> + - ti,am4372-scm-conf
[Severity: Medium]
Does this cause make dtbs_check to report undocumented compatible warnings
for the newly added TI platforms?
Since these new compatibles are introduced in this exclusion list but are
not defined under a standard properties compatible block in syscon.yaml
or another dedicated schema, it appears the tooling will fail to extract
them. Will this lead to schema validation skipping hardware-specific
constraints for these TI platforms?
> + - ti,dm814-scm-conf
> + - ti,dm8168-scm-conf
> + - ti,dra7-scm-conf
> + - ti,omap2-scm-conf
> + - ti,omap3-scm-conf
> + - ti,omap4-sysc-padconf-global
> + - ti,omap5-scm-conf
> + - ti,omap5-scm-wkup-conf
> + then:
> + required:
> + - incorrect-usage-of-simple-bus-and-syscon
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260608-n-dt-bindings-simple-bus-syscon-v2-0-0203e6c249dc@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-06-08 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 13:54 [PATCH v2 0/4] dt-bindings: mfd: syscon: Tighten checks Krzysztof Kozlowski
2026-06-08 13:54 ` [PATCH v2 1/4] dt-bindings: mfd: syscon: Disallow simple-bus with syscon Krzysztof Kozlowski
2026-06-08 14:06 ` sashiko-bot [this message]
2026-06-08 13:54 ` [PATCH v2 2/4] dt-bindings: mfd: syscon: Drop unneeded case for syscon + simple-mfd Krzysztof Kozlowski
2026-06-08 14:08 ` sashiko-bot
2026-06-08 13:54 ` [PATCH v2 3/4] dt-bindings: mfd: syscon: Drop custom select for older dtschema Krzysztof Kozlowski
2026-06-08 14:01 ` sashiko-bot
2026-06-08 14:07 ` Krzysztof Kozlowski
2026-06-08 13:54 ` [PATCH v2 4/4] ARM: dts: ti: Add specific compatibles for SCM conf nodes Krzysztof Kozlowski
2026-06-08 14:11 ` 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=20260608140650.CF8DE1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=robh@kernel.org \
--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