From: sashiko-bot@kernel.org
To: "Dinh Nguyen" <dinguyen@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCHv2 1/2] dt-bindings: i3c: dw: add resets and reset-names
Date: Wed, 27 May 2026 18:03:06 +0000 [thread overview]
Message-ID: <20260527180306.BAEE71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260527174221.79259-1-dinguyen@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] The commit documents `reset-names` for a single-entry reset, which violates DT binding guidelines and codifies a brittle pattern in the driver that causes silent hardware failures if the name is omitted in the DTS.
--
commit 5db0a7d3c21cf60d537f37725a5d5312d88c8c4f
Author: Dinh Nguyen <dinguyen@kernel.org>
dt-bindings: i3c: dw: add resets and reset-names
This commit updates the snps,dw-i3c-master binding to document the core
reset signal. It adds both the resets and reset-names properties to match
what the driver currently expects.
> diff --git a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> index e803457d3f554..7a39fe62bbbc0 100644
> --- a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> +++ b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> @@ -35,6 +35,14 @@ properties:
> - const: core
> - const: apb
>
> + resets:
> + items:
> + - description: Core reset signal
> +
> + reset-names:
> + items:
> + - const: core_rst
> +
[Severity: High]
This is a pre-existing issue, but documenting reset-names for a single-entry
reset codifies a brittle pattern in the driver that can cause silent hardware
failures.
DT binding guidelines recommend skipping *-names for single-entry lists.
Because reset-names is not marked as required, a DTS author could provide
a valid resets property without reset-names.
If this happens, the driver's call to request "core_rst" will fail to find
the name. Since the request is optional, it returns a NULL reset handle
instead of an error. The driver will silently proceed, but calls to assert the
reset will be no-ops, potentially leading to hardware lockups.
Should we drop reset-names from this binding and instead update the driver to
request the single reset by passing NULL instead of "core_rst"?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260527174221.79259-1-dinguyen@kernel.org?part=1
next prev parent reply other threads:[~2026-05-27 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 17:42 [PATCHv2 1/2] dt-bindings: i3c: dw: add resets and reset-names Dinh Nguyen
2026-05-27 17:42 ` [PATCHv2 2/2] arm64: dts: socfpga: agilex5: popuplate reset properties for I3C Dinh Nguyen
2026-05-27 18:01 ` sashiko-bot
2026-05-27 18:03 ` sashiko-bot [this message]
2026-05-28 7:20 ` [PATCHv2 1/2] dt-bindings: i3c: dw: add resets and reset-names Krzysztof Kozlowski
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=20260527180306.BAEE71F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--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