From: sashiko-bot@kernel.org
To: "Nikolai Burov" <nikolai.burov@jolla.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: power: Add MediaTek MT6858 power domain controller
Date: Tue, 14 Jul 2026 13:49:08 +0000 [thread overview]
Message-ID: <20260714134909.4F8081F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714-mt6858-pmdomain-v1-1-4f09bbb822e0@jolla.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The conditional block for 'mediatek,mt6858-power-controller' defines 6 items for 'access-controllers' but omits 'minItems: 6', allowing device trees with incomplete configurations to silently pass validation.
- [Medium] Increasing the global `maxItems` for `access-controllers` from 3 to 6 relaxes validation constraints for older compatible strings.
--
--- Patch [1]: [PATCH 1/3] dt-bindings: power: Add MediaTek MT6858 power domain controller ---
commit 45a85a0c0fa43cfb779c99ce538116e8c4ab742f
Author: Nikolai Burov <nikolai.burov@jolla.com>
dt-bindings: power: Add MediaTek MT6858 power domain controller
Add a new compatible and document bindings for the power domain
controller of the MT6858 SoC.
> diff --git a/Documentation/devicetree/bindings/power/mediatek,power-controller.yaml b/Documentation/devicetree/bindings/power/mediatek,power-controller.yaml
> index 07f046277f8a6..eecb95323bfbe 100644
> --- a/Documentation/devicetree/bindings/power/mediatek,power-controller.yaml
> +++ b/Documentation/devicetree/bindings/power/mediatek,power-controller.yaml
[ ... ]
> @@ -55,7 +56,7 @@ properties:
> faults while enabling or disabling a power domain.
> For example, this may hold phandles to INFRACFG and SMI.
> minItems: 1
> - maxItems: 3
> + maxItems: 6
[Severity: Medium]
Does increasing the global maxItems to 6 inadvertently relax the validation
constraints for older compatible strings (such as MT6735 or MT6795) that were
previously capped at 3? Should the tighter bounds be explicitly maintained for
those older platforms using an if-then block?
>
> patternProperties:
> "^power-domain@[0-9a-f]+$":
[ ... ]
> @@ -155,6 +157,23 @@ required:
> - compatible
>
> allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - mediatek,mt6858-power-controller
> + then:
> + properties:
> + access-controllers:
> + items:
> + - description: handle to INFRACFG register block
> + - description: handle to IMG_SUB0 register block
> + - description: handle to CAM_SUB1 register block
> + - description: handle to CAM_SUB0 register block
> + - description: handle to IPE_SUB0 register block
> + - description: handle to VLPCFG register block
[Severity: Medium]
Should there be a minItems: 6 constraint added to this block to enforce the
presence of all 6 items? Without it, would an incomplete MT6858 device tree
that provides fewer than 6 controllers silently pass validation?
> +
> - if:
> properties:
> compatible:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-mt6858-pmdomain-v1-0-4f09bbb822e0@jolla.com?part=1
next prev parent reply other threads:[~2026-07-14 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 13:43 [PATCH 0/3] pmdomain: mediatek: Add MT6858 support Nikolai Burov via B4 Relay
2026-07-14 13:43 ` [PATCH 1/3] dt-bindings: power: Add MediaTek MT6858 power domain controller Nikolai Burov via B4 Relay
2026-07-14 13:49 ` sashiko-bot [this message]
2026-07-14 13:43 ` [PATCH 2/3] pmdomain: mediatek: Add support for secure modem power domain control Nikolai Burov via B4 Relay
2026-07-14 13:51 ` sashiko-bot
2026-07-14 15:28 ` Matthias Brugger
2026-07-14 13:43 ` [PATCH 3/3] pmdomain: mediatek: Add support for MT6858 SoC Nikolai Burov via B4 Relay
2026-07-14 13:58 ` 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=20260714134909.4F8081F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=nikolai.burov@jolla.com \
--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