From: sashiko-bot@kernel.org
To: "Rohan Joshi" <rohan1sj@cadence.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: mmc: cdns,sdhci: Add CQE support
Date: Tue, 25 Aug 2026 11:17:47 +0000 [thread overview]
Message-ID: <20260825111748.1FEE11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260825-cdns_sdhci_cqe-support-v4-1-e9f72e338373@cadence.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `else` block for non-Elba platforms lacks explicit `maxItems: 2` constraints for `reg` and `reg-names`, creating a validation loophole that allows non-Elba platforms to define an invalid third register.
--
--- Patch [1]: [PATCH v4 1/2] dt-bindings: mmc: cdns,sdhci: Add CQE support ---
commit 48a4d35cce2e12157d9c52de4ba805fd4e404597
Author: Rohan Joshi <rohan1sj@cadence.com>
dt-bindings: mmc: cdns,sdhci: Add CQE support
This commit adds an optional cqhci named resource to map the CQE register
space. It updates the amd,pensando-elba platform to include this resource
while maintaining compatibility for platforms without the CQE block.
> diff --git a/Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml b/Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml
> --- a/Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml
> +++ b/Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml
[ ... ]
> @@ -131,13 +138,27 @@ allOf:
> then:
> properties:
> reg:
> + minItems: 2
> items:
> - description: Host controller registers
> - description: Elba byte-lane enable register for writes
> + - description: CQE (Command Queuing Engine) registers (optional)
> + reg-names:
> + minItems: 2
> + items:
> + - const: hc
> + - const: bctl
> + - const: cqhci
> else:
> properties:
> reg:
> - maxItems: 1
> + items:
> + - description: Host Controller registers
> + - description: CQE (Command Queuing Engine) registers (optional)
> + reg-names:
> + items:
> + - const: hc
> + - const: cqhci
[Severity: Low]
Since the top-level schema was updated to permit up to 3 items for reg, does
omitting an explicit maxItems limit in this else block allow non-Elba
platforms to define an invalid third register and silently pass validation?
In dt-schema, an items list inside an if/then/else block does not restrict
the overall length unless maxItems is explicitly defined.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260825-cdns_sdhci_cqe-support-v4-0-e9f72e338373@cadence.com?part=1
next prev parent reply other threads:[~2026-08-25 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 11:10 [PATCH v4 0/2] CQE support for cadence eMMC host controller Rohan Joshi via B4 Relay
2026-08-25 11:10 ` Rohan Joshi
2026-08-25 11:10 ` [PATCH v4 1/2] dt-bindings: mmc: cdns,sdhci: Add CQE support Rohan Joshi via B4 Relay
2026-08-25 11:10 ` Rohan Joshi
2026-08-25 11:17 ` sashiko-bot [this message]
2026-08-25 11:35 ` Krzysztof Kozlowski
2026-08-25 11:10 ` [PATCH v4 2/2] mmc: sdhci-cadence: " Rohan Joshi via B4 Relay
2026-08-25 11:10 ` Rohan Joshi
2026-08-25 11:24 ` sashiko-bot
2026-08-25 11:38 ` Krzysztof Kozlowski
2026-08-27 12:20 ` Adrian Hunter
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=20260825111748.1FEE11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rohan1sj@cadence.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.