From: sashiko-bot@kernel.org
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
conor+dt@kernel.org, robh@kernel.org, lee@kernel.org
Subject: Re: [PATCH 01/10] dt-bindings: mfd: ene-kb[3]930: Use generic power-controller schema
Date: Tue, 04 Aug 2026 15:11:27 +0000 [thread overview]
Message-ID: <20260804151128.3DA7B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804-mfd-syspower-v1-1-a440783c2e78@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Broken schema reference to non-existent power-controller.yaml
--
--- Patch [1]: [PATCH 01/10] dt-bindings: mfd: ene-kb[3]930: Use generic power-controller schema ---
commit 7180a65c7f429628f30dced562271d7d6ecc790b
Author: Peng Fan <peng.fan@nxp.com>
dt-bindings: mfd: ene-kb[3]930: Use generic power-controller schema
Convert the binding to use the generic power-controller schema instead by
referencing power-controller.yaml and removing the local
system-power-controller property definition.
> diff --git a/Documentation/devicetree/bindings/mfd/ene-kb3930.yaml b/Documentation/devicetree/bindings/mfd/ene-kb3930.yaml
> index 9b11b6e2bbf74..1847a6d5b22e8 100644
> --- a/Documentation/devicetree/bindings/mfd/ene-kb3930.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ene-kb3930.yaml
> @@ -13,6 +13,9 @@ description: |
> maintainers:
> - Lubomir Rintel <lkundrak@v3.sk>
>
> +allOf:
> + - $ref: /schemas/power/power-controller.yaml#
[Severity: Low]
Does the /schemas/power/power-controller.yaml schema exist in the tree?
If the generic power-controller properties are only defined in a legacy text
binding (Documentation/devicetree/bindings/power/power-controller.txt) and
have not yet been converted to YAML, make dt_binding_check will fail because
this reference cannot be resolved.
Additionally, since unevaluatedProperties is set to false, will removing the
local system-power-controller property definition cause the example to be
rejected as having an undocumented property?
[ ... ]
> diff --git a/Documentation/devicetree/bindings/mfd/ene-kb930.yaml b/Documentation/devicetree/bindings/mfd/ene-kb930.yaml
> index 02c111def5de5..e0c8abf95bd92 100644
> --- a/Documentation/devicetree/bindings/mfd/ene-kb930.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ene-kb930.yaml
> @@ -13,7 +13,9 @@ description: |
> maintainers:
> - Dmitry Osipenko <digetx@gmail.com>
>
> -$ref: /schemas/power/supply/power-supply.yaml
> +allOf:
> + - $ref: /schemas/power/supply/power-supply.yaml
> + - $ref: /schemas/power/power-controller.yaml#
[Severity: Low]
Similarly, will this reference to a non-existent schema file break
dt_binding_check validation here?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260804-mfd-syspower-v1-0-a440783c2e78@nxp.com?part=1
next prev parent reply other threads:[~2026-08-04 15:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 14:16 [PATCH 00/10] dt-bindings: mfd: Use generic power-controller schema Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 14:16 ` [PATCH 01/10] dt-bindings: mfd: ene-kb[3]930: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:11 ` sashiko-bot [this message]
2026-08-04 14:16 ` [PATCH 02/10] dt-bindings: mfd: ti,tps65910: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:23 ` sashiko-bot
2026-08-05 21:12 ` Rob Herring
2026-08-05 21:12 ` Rob Herring
2026-08-04 14:16 ` [PATCH 03/10] dt-bindings: mfd: rockchip,rk8x: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:30 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 04/10] dt-bindings: mfd: ricoh,rn5t618: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:34 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 05/10] dt-bindings: mfd: netronix,ntxec: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:44 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 06/10] dt-bindings: mfd: ti,twl: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:51 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 07/10] dt-bindings: mfd: ti,tps6594: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 15:55 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 08/10] dt-bindings: mfd: rohm,bd71828-pmic: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 16:01 ` sashiko-bot
2026-08-05 7:14 ` Matti Vaittinen
2026-08-05 7:14 ` Matti Vaittinen
2026-08-04 14:16 ` [PATCH 09/10] dt-bindings: mfd: fsl,mc13xxx: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 16:10 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 10/10] dt-bindings: mfd: samsung,s2mpg10-pmic: " Peng Fan (OSS)
2026-08-04 14:16 ` Peng Fan (OSS)
2026-08-04 16:14 ` sashiko-bot
2026-08-05 21:10 ` [PATCH 00/10] dt-bindings: mfd: " Rob Herring
2026-08-05 21:10 ` Rob Herring
2026-08-06 1:11 ` Peng Fan
2026-08-06 1:11 ` Peng Fan
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=20260804151128.3DA7B1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=peng.fan@oss.nxp.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 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.