From: sashiko-bot@kernel.org
To: "Sasha Finkelstein" <k@chaosmail.tech>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 1/6] dt-bindings: spmi: apple,spmi: Add t603x and t8122
Date: Sun, 16 Aug 2026 10:30:51 +0000 [thread overview]
Message-ID: <20260816103052.692211F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260816-t603x-spmi-v6-1-c5ab87aa447b@chaosmail.tech>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding introduces interrupt controller provider capabilities but fails to add the mandatory properties to the `required` list, violating subsystem guidelines.
--
--- Patch [1]: [PATCH v6 1/6] dt-bindings: spmi: apple,spmi: Add t603x and t8122 ---
commit 55496611e1596aed1ddc4ec7dccafdc5fc8fb28b
Author: Sasha Finkelstein <k@chaosmail.tech>
dt-bindings: spmi: apple,spmi: Add t603x and t8122
This commit adds t603x and t8122 compatibles, interrupt support, and
support for SPMI controllers that are not always-on to the apple,spmi
binding.
> diff --git a/Documentation/devicetree/bindings/spmi/apple,spmi.yaml b/Documentation/devicetree/bindings/spmi/apple,spmi.yaml
> --- a/Documentation/devicetree/bindings/spmi/apple,spmi.yaml
> +++ b/Documentation/devicetree/bindings/spmi/apple,spmi.yaml
[ ... ]
> @@ -34,6 +37,18 @@ properties:
> reg:
> maxItems: 1
>
> + interrupts:
> + maxItems: 1
> + description: Optional, operates in polled mode if not present
> +
> + interrupt-controller: true
> +
> + "#interrupt-cells":
> + const: 2
> +
> + power-domains:
> + maxItems: 1
> +
> required:
> - compatible
> - reg
[Severity: Medium]
The commit message notes that the interrupt controller functionality is kept
optional since it is only needed on 3 out of 10 controllers. However, does
leaving these properties out of the required block allow incomplete device
tree nodes to pass schema validation?
According to the subsystem guidelines for hardware variants, when new provider
capabilities are added, the corresponding properties like interrupt-controller
and "#interrupt-cells" must be included in the required list.
Should these properties be added to the required list under an if-then block
matching the specific hardware variations that support this functionality, or
should a dependency be added to ensure that "#interrupt-cells" is always present
when interrupt-controller is used?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260816-t603x-spmi-v6-0-c5ab87aa447b@chaosmail.tech?part=1
next prev parent reply other threads:[~2026-08-16 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 10:26 [PATCH v6 0/6] spmi: apple: Additional commands and interrupt support Sasha Finkelstein
2026-08-16 10:26 ` [PATCH v6 1/6] dt-bindings: spmi: apple,spmi: Add t603x and t8122 Sasha Finkelstein
2026-08-16 10:30 ` sashiko-bot [this message]
2026-08-16 10:26 ` [PATCH v6 2/6] spmi: apple: Validate FIFO state Sasha Finkelstein
2026-08-16 10:37 ` sashiko-bot
2026-08-16 10:26 ` [PATCH v6 3/6] spmi: apple: check transaction status Sasha Finkelstein
2026-08-16 10:37 ` sashiko-bot
2026-08-16 10:26 ` [PATCH v6 4/6] spmi: apple: Implement remaining commands Sasha Finkelstein
2026-08-16 10:36 ` sashiko-bot
2026-08-16 10:26 ` [PATCH v6 5/6] spmi: apple: lock around FIFOs Sasha Finkelstein
2026-08-16 10:26 ` [PATCH v6 6/6] spmi: apple: Add interrupt functionality Sasha Finkelstein
2026-08-16 10:38 ` 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=20260816103052.692211F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=k@chaosmail.tech \
--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