Re: [PATCH 0/5] Add driver for Qualcomm QGauge (qcom_qg) fuel gauge
From: Majid Hajiheidari
Date: Sat Nov 14 2026 - 20:23:05 EST
Hi Val,
On Thu, 12 Nov 2026 14:07:26 -0300, Val Packett wrote:
> This series adds a driver for the "qgauge" battery fuel gauge
> present in Qualcomm PMICs like PMI632, PM6150, PM7250B, PM2250.
> The PMI632 is used in SDM632, SM6115/SM4250, SM6125 based phones.
I tried v1 on an SM6125 phone, a Xiaomi Mi A3 (sm6125-xiaomi-laurel-sprout,
PMI632), on top of next-20261113. Board side: the node enabled with
monitored-battery (simple-battery with the OCV table from the stock
profile), io-channels = <&pmi632_adc ADC5_BAT_THERM_100K_PU> as
"batt-therm" and power-supplies = <&pmi632_typec>.
It probes without any kernel log output and reports sane values:
capacity 66
voltage_now 3979548 (vbat_sns from the ADC: 3.98 V)
voltage_avg 3979937
current_now -72631
temp 297 (SoC TSENS zones: 29-30 C)
charge_full 4048000 (design 4030000, so the SDAM read works)
health Good
status Charging
Two things I noticed:
- voltage_ocv returns -ENODATA ("No data available") while capacity is
reported at the same time. Is that intended, e.g. the PON OCV being
used for capacity but not exposed?
- status is derived only from power_supply_am_i_supplied(), so it says
Charging whenever USB is connected. On my phone the charger float
voltage is limited to 3.96 V with a local patch and the battery sits at
3.98 V, so current_now stays at about -70 mA (discharging) while status
reads Charging. I would expect the same once a battery is full. Would
it make sense to report Not charging / Full based on the current?
Tested-by: Majid Hajiheidari <majidhhdri@xxxxxxxxx> # sm6125-xiaomi-laurel-sprout
Happy to test v2 as well.
Thanks,
Majid