Devicetree
 help / color / mirror / Atom feed
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 5/5] arm64: dts: qcom: pmi632: Add battery fuel gauge node
Date: Thu, 12 Nov 2026 17:30:39 +0000	[thread overview]
Message-ID: <sashiko-outbox-211597@kernel.org> (raw)
In-Reply-To: <20261112170841.2189322-6-val@packett.cool>

Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Low] arm64: dts: qcom: pmi632: fuel-gauge@4800 violates
  qcom,spmi-pmic.yaml schema
- [Low] arm64: dts: qcom: pmi632: missing io-channels in pmi632_qgauge
  node
--

commit 15ccef39df06d430c96a1c58092319c5e86db8a5
Author: Val Packett <val@packett.cool>

arm64: dts: qcom: pmi632: Add battery fuel gauge node

This commit adds devicetree nodes for the PMI632 qgauge battery fuel gauge
at 0x4800 and the SDAM region at 0xb100.

> diff --git a/arch/arm64/boot/dts/qcom/pmi632.dtsi b/arch/arm64/boot/dts/qcom/pmi632.dtsi
> index 85cef103e00dc..f04d65fb7aabb 100644
> --- a/arch/arm64/boot/dts/qcom/pmi632.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pmi632.dtsi
> @@ -163,11 +163,44 @@ pmi632_adc_tm: adc-tm@3500 {
>  			status = "disabled";
>  		};
>  
> +		pmi632_qgauge: fuel-gauge@4800 {
> +			compatible = "qcom,pmi632-qg";

[Severity: Low]
Does adding fuel-gauge@4800 under pmic@2 break dtbs_check against
Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml?

That schema matches "qcom,pmi632" and sets additionalProperties: false,
but its patternProperties do not list "^fuel-gauge@[0-9a-f]+$" referencing
/schemas/power/supply/qcom,qg.yaml#.

> +
> +			reg = <0x4800>;
> +
> +			interrupts = <0x2 0x48 0x0 IRQ_TYPE_EDGE_BOTH>,
> +				     <0x2 0x48 0x1 IRQ_TYPE_EDGE_BOTH>,
> +				     <0x2 0x48 0x2 IRQ_TYPE_EDGE_RISING>,
> +				     <0x2 0x48 0x3 IRQ_TYPE_EDGE_RISING>,
> +				     <0x2 0x48 0x4 IRQ_TYPE_EDGE_RISING>,
> +				     <0x2 0x48 0x5 IRQ_TYPE_EDGE_RISING>,
> +				     <0x2 0x48 0x6 IRQ_TYPE_EDGE_RISING>;
> +			interrupt-names = "batt-missing",
> +					  "vbat-low",
> +					  "vbat-empty",
> +					  "fifo-done",
> +					  "good-ocv",
> +					  "fsm-state-chg",
> +					  "event";
> +
> +			nvmem = <&pmi632_sdam_2>;
> +
> +			status = "disabled";
> +		};

[Severity: Low]
Should pmi632_qgauge also wire up io-channels = <&pmi632_adc
ADC5_BAT_THERM_100K_PU> and io-channel-names = "batt-therm" here?

Earlier in this series, commit "arm64: dts: qcom: pmi632: Add missing
bat_therm ADC channel" added channel@4a to pmi632_adc for the fuel gauge.
Without io-channels on pmi632_qgauge (or in every board DTS),
qcom_qg_probe() leaves qg->batt_therm NULL, causing temperature reads to
fail with -ENODEV, qg_get_capacity() to fall back to a hardcoded 25 C, and
qg_get_health() to skip temperature fault checks.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261112170841.2189322-1-val@packett.cool?part=5

      reply	other threads:[~2026-11-12 17:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 17:07 [PATCH 0/5] Add driver for Qualcomm QGauge (qcom_qg) fuel gauge Val Packett
2026-11-12 17:07 ` [PATCH 1/5] dt-bindings: power: supply: add Qualcomm QGauge " Val Packett
2026-11-12 17:20   ` sashiko-bot
2026-11-12 17:07 ` [PATCH 2/5] power: supply: add Qualcomm QGauge (qcom_qg) fuel gauge driver Val Packett
2026-11-12 17:29   ` sashiko-bot
2026-11-12 17:07 ` [PATCH 3/5] iio: adc: qcom-spmi-adc5: Add ADC5_BAT_THERM_100K_PU Val Packett
2026-11-12 17:07 ` [PATCH 4/5] arm64: dts: qcom: pmi632: Add missing bat_therm ADC channel Val Packett
2026-11-12 17:07 ` [PATCH 5/5] arm64: dts: qcom: pmi632: Add battery fuel gauge node Val Packett
2026-11-12 17:30   ` sashiko-bot [this message]

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-211597@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