All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nihal Kumar Gupta" <nihal.gupta@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/6] arm64: dts: qcom: glymur-crd: Add PM8010 camera PMIC
Date: Mon, 07 Sep 2026 10:20:49 +0000	[thread overview]
Message-ID: <20260907102050.3F2201F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907-glymur_camss_dts-v1-4-6c2ced5ea5f9@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The device tree node uses an undocumented and unsupported compatible string 'qcom,pm8010-i2c' with no corresponding dt-bindings or driver implementations in the kernel tree.
- [Medium] The PM8010 PMIC node is missing an `interrupts` property, which is architecturally necessary for I2C PMICs to signal thermal alarms and faults.
--

commit c57ad5fec12bca214fc8171c9ab4ce19cbc0631e
Author: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>

arm64: dts: qcom: glymur-crd: Add PM8010 camera PMIC

This commit adds a new device tree node for the PM8010 PMIC over I2C to the 
Glymur CRD. It configures the PMIC's seven LDO regulators, reset GPIO, and 
associated pinctrl states.

> diff --git a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> index 4df3ccfee106a..68a191890b7d8 100644
> --- a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> @@ -671,6 +671,66 @@ ptn3222_1: redriver@47 {
>  
>  		#phy-cells = <0>;
>  	};
> +
> +	pm8010: pmic@8 {
> +		compatible = "qcom,pm8010-i2c";

[Severity: Medium]
Will this compatible string match an existing driver? The "qcom,pm8010-i2c" 
compatible string appears to be undocumented and unsupported in the kernel
tree.

When building device trees with make dtbs_check, this will result in 
validation failures since there are no corresponding dt-bindings. The pm8010
device node will also remain inactive because no driver core can match it, 
leaving the PMIC and its regulators uninitialized.

> +		reg = <0x8>;
> +
> +		reset-gpios = <&tlmm 106 GPIO_ACTIVE_LOW>;
> +
> +		vdd-l1-l2-supply = <&vreg_l6p>;

[Severity: Medium]
Should this PM8010 PMIC node include an interrupts property?

The pm8010 node in arch/arm64/boot/dts/qcom/glymur-crd.dtsi defines a reset
line but is missing an interrupt line, which is architecturally necessary
for I2C PMICs to signal thermal alarms and faults.

Without an interrupt line, the SoC cannot respond to critical PMIC hardware
events like over-temperature or over-current faults. Additionally, if a 
future driver follows standard Qualcomm I2C PMIC patterns, passing a missing
IRQ to devm_regmap_add_irq_chip_fwnode() will cause the driver probe to fail
entirely with -EINVAL.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260907-glymur_camss_dts-v1-0-6c2ced5ea5f9@oss.qualcomm.com?part=4

  reply	other threads:[~2026-09-07 10:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 10:07 [PATCH 0/6] Add CCI and CAMSS support for Glymur Nihal Kumar Gupta
2026-09-07 10:07 ` [PATCH 1/6] arm64: dts: qcom: glymur: Add CAMSS and CSIPHY nodes " Nihal Kumar Gupta
2026-09-07 10:26   ` sashiko-bot
2026-09-07 10:07 ` [PATCH 2/6] arm64: dts: qcom: glymur: Add CCI definitions " Nihal Kumar Gupta
2026-09-07 10:47   ` Abel Vesa
2026-09-07 10:07 ` [PATCH 3/6] arm64: dts: qcom: glymur: Add camera MCLK pinctrl Nihal Kumar Gupta
2026-09-07 10:47   ` Abel Vesa
2026-09-07 10:07 ` [PATCH 4/6] arm64: dts: qcom: glymur-crd: Add PM8010 camera PMIC Nihal Kumar Gupta
2026-09-07 10:20   ` sashiko-bot [this message]
2026-09-07 10:07 ` [PATCH 5/6] arm64: dts: qcom: glymur-crd: Add ov08x40 RGB sensor on CSIPHY4 Nihal Kumar Gupta
2026-09-07 10:47   ` Abel Vesa
2026-09-07 10:07 ` [PATCH 6/6] arm64: defconfig: Enable OV08X40 camera sensor driver Nihal Kumar Gupta

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=20260907102050.3F2201F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=nihal.gupta@oss.qualcomm.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.