From: sashiko-bot@kernel.org
To: "Sasha Finkelstein" <k@chaosmail.tech>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v10 1/6] dt-bindings: spmi: apple,spmi: Add t603x and t8122
Date: Fri, 02 Oct 2026 09:13:46 +0000 [thread overview]
Message-ID: <20261002091346.A16C91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261001-t603x-spmi-v10-1-ff815c66c73f@chaosmail.tech>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: spmi: apple: missing power-domains in required list for non-always-on SoCs
--
commit 888cdba0f17c299db4b50bbf52f14fcb099ef7c9
Author: Sasha Finkelstein <k@chaosmail.tech>
dt-bindings: spmi: apple,spmi: Add t603x and t8122
This commit adds new t603x and t8122 compatibles to the apple,spmi bindings.
It also introduces optional interrupt properties and adds support for SPMI
controllers that are not always-on.
> diff --git a/Documentation/devicetree/bindings/spmi/apple,spmi.yaml b/Documentation/devicetree/bindings/spmi/apple,spmi.yaml
> index 3e5b14bc8c317..4e73083ecec33 100644
> --- a/Documentation/devicetree/bindings/spmi/apple,spmi.yaml
> +++ b/Documentation/devicetree/bindings/spmi/apple,spmi.yaml
[ ... ]
> @@ -34,10 +37,36 @@ 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
>
> +if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - apple,t8122-spmi
> + - apple,t6030-spmi
> + - apple,t6031-spmi
> +then:
> + required:
> + - interrupt-controller
> + - "#interrupt-cells"
> + - interrupts
[Severity: Medium]
Should power-domains be included in this required list?
If a device tree for a non-always-on Apple SoC, such as t8122-spmi or
t6030-spmi, is authored without the power-domains property, the schema
validation will incorrectly accept it as valid due to the missing constraint
in this block.
At runtime, the kernel will fail to attach the power domain, resulting in a
fatal synchronous external abort and system panic when the driver accesses
unpowered registers.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001-t603x-spmi-v10-0-ff815c66c73f@chaosmail.tech?part=1
next prev parent reply other threads:[~2026-10-02 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 20:26 [PATCH v10 0/6] spmi: apple: Additional commands and interrupt support Sasha Finkelstein
2026-10-01 20:26 ` [PATCH v10 1/6] dt-bindings: spmi: apple,spmi: Add t603x and t8122 Sasha Finkelstein
2026-10-02 9:13 ` sashiko-bot [this message]
2026-10-01 20:26 ` [PATCH v10 2/6] spmi: apple: Validate FIFO state Sasha Finkelstein
2026-10-01 20:26 ` [PATCH v10 3/6] spmi: apple: check transaction status Sasha Finkelstein
2026-10-01 20:26 ` [PATCH v10 4/6] spmi: apple: Implement remaining commands Sasha Finkelstein
2026-10-02 9:13 ` sashiko-bot
2026-10-01 20:27 ` [PATCH v10 5/6] spmi: apple: lock around FIFOs Sasha Finkelstein
2026-10-02 9:13 ` sashiko-bot
2026-10-01 20:27 ` [PATCH v10 6/6] spmi: apple: Add interrupt functionality Sasha Finkelstein
2026-10-02 9:13 ` 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=20261002091346.A16C91F000FF@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