From: sashiko-bot@kernel.org
To: "Val Packett" <val@packett.cool>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/6] arm64: dts: qcom: pmi632: Add LCDB regulator node
Date: Mon, 09 Nov 2026 22:22:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-205717@kernel.org> (raw)
In-Reply-To: <20261109221453.658316-4-val@packett.cool>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] arm64: dts: qcom: pmi632: undocumented regulator@ec00 breaks
dtbs_check
--
commit 59a61b0cda3ab4cae16c1eae412c4c0a133346c4
Author: Val Packett <val@packett.cool>
arm64: dts: qcom: pmi632: Add LCDB regulator node
This commit adds the pmi632_lcdb LCD bias regulator node and its ldo and
ncp child nodes to pmi632.dtsi.
> diff --git a/arch/arm64/boot/dts/qcom/pmi632.dtsi b/arch/arm64/boot/dts/qcom/pmi632.dtsi
> index b0ed35094a98d..ab850050eb22a 100644
> --- a/arch/arm64/boot/dts/qcom/pmi632.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pmi632.dtsi
> @@ -204,5 +204,19 @@ pmi632_vib: vibrator@5700 {
> reg = <0x5700>;
> status = "disabled";
> };
> +
> + pmi632_lcdb: regulator@ec00 {
> + compatible = "qcom,pmi632-lcdb", "qcom,pm8150l-lcdb";
> + reg = <0xec00>;
> + interrupts = <0x3 0xec 0x1 IRQ_TYPE_EDGE_RISING>;
> +
> + status = "disabled";
> +
> + pmi632_lcdb_ldo: ldo {
> + };
> +
> + pmi632_lcdb_ncp: ncp {
> + };
> + };
> };
> };
[Severity: Medium]
Are the Devicetree binding schema and driver for qcom,pmi632-lcdb and
qcom,pm8150l-lcdb missing from the tree?
Neither compatible string is documented under
Documentation/devicetree/bindings/ or matched by an in-tree regulator
driver, and Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml has
additionalProperties: false without a pattern permitting regulator@[0-9a-f]+
child nodes. Adding regulator@ec00 causes dtbs_check schema validation
failures on every board DTB that includes pmi632.dtsi, and boards enabling
pmi632_lcdb will fail to resolve the pmi632_lcdb_ldo and pmi632_lcdb_ncp
supplies at runtime.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109221453.658316-1-val@packett.cool?part=3
next prev parent reply other threads:[~2026-11-09 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 22:14 [PATCH 0/6] arm64: dts: qcom: Add Moto G9 Play (guamp) / Power (cebu) Val Packett
2026-11-09 22:14 ` [PATCH 1/6] dt-bindings: arm: qcom: Add Motorola Moto G9 Play Val Packett
2026-11-09 22:14 ` [PATCH 2/6] dt-bindings: arm: qcom: Add Motorola Moto G9 Power Val Packett
2026-11-09 22:14 ` [PATCH 3/6] arm64: dts: qcom: pmi632: Add LCDB regulator node Val Packett
2026-11-09 22:22 ` sashiko-bot [this message]
2026-11-09 22:26 ` Val Packett
2026-11-09 22:14 ` [PATCH 4/6] arm64: dts: qcom: Add sm6115-motorola-common Val Packett
2026-11-09 22:33 ` Val Packett
2026-11-09 22:47 ` sashiko-bot
2026-11-09 22:14 ` [PATCH 5/6] arm64: dts: qcom: sm6115: Add Motorola Moto G9 Play (guamp) Val Packett
2026-11-09 22:29 ` sashiko-bot
2026-11-09 22:14 ` [PATCH 6/6] arm64: dts: qcom: sm6115: Add Motorola Moto G9 Power (cebu) Val Packett
2026-11-09 22:35 ` 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=sashiko-outbox-205717@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=val@packett.cool \
/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