From: "Adil Hüsrev Tepe" <tadilhusrev@gmail.com>
To: Sebastian Reichel <sre@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: "Yassine Oudjana" <y.oudjana@protonmail.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Adil Hüsrev Tepe" <tadilhusrev@gmail.com>
Subject: [PATCH v1 0/3] power: supply: s2mu005-battery: add S2MU106 (Samsung Galaxy XCover5)
Date: Mon, 16 Nov 2026 10:39:57 +0300 [thread overview]
Message-ID: <20261116074000.355176-1-tadilhusrev@gmail.com> (raw)
This series adds support for the Samsung S2MU106 PMIC fuel gauge to the
existing s2mu005-battery driver, for the Samsung Galaxy XCover5
(Exynos850).
The S2MU106 fuel gauge shares the S2MU005's direct voltage, current and
state-of-charge registers and their scaling. This was verified on an
XCover5: with the s2mu005 driver bound to the S2MU106 gauge, voltage,
state of charge and the sign of the charge current all read correctly.
It does not, however, share the MONOUT average-monitoring path, so the
S2MU106 variant exposes only the instantaneous values. The XCover5 also
does not wire the gauge's alert line, which patch 2 accommodates.
1 dt-bindings: add samsung,s2mu106-fuel-gauge
2 make the alert interrupt optional
3 add S2MU106 support
Based on v7.4-rc1.
Tool usage
----------
Prepared during XCover5 mainline bring-up with an AI coding assistant
(Claude Code, Anthropic): it compared the S2MU005/S2MU106 fuel-gauge
register maps, drafted these changes and changelogs, and ran a live A/B
comparison on the device under my direction. I reviewed every line,
tested on hardware, and take responsibility for the series. Review
comments are welcome and I will answer them myself.
Adil Hüsrev Tepe (3):
dt-bindings: power: supply: samsung,s2mu005-fuel-gauge: add S2MU106
power: supply: s2mu005-battery: make the alert interrupt optional
power: supply: s2mu005-battery: add S2MU106 support
.../supply/samsung,s2mu005-fuel-gauge.yaml | 7 +-
drivers/power/supply/s2mu005-battery.c | 71 +++++++++++++++----
2 files changed, 63 insertions(+), 15 deletions(-)
--
2.53.0
next reply other threads:[~2026-11-16 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 7:39 Adil Hüsrev Tepe [this message]
2026-11-16 7:39 ` [PATCH v1 1/3] dt-bindings: power: supply: samsung,s2mu005-fuel-gauge: add S2MU106 Adil Hüsrev Tepe
2026-11-16 7:55 ` sashiko-bot
2026-11-16 7:39 ` [PATCH v1 2/3] power: supply: s2mu005-battery: make the alert interrupt optional Adil Hüsrev Tepe
2026-11-16 7:40 ` [PATCH v1 3/3] power: supply: s2mu005-battery: add S2MU106 support Adil Hüsrev Tepe
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=20261116074000.355176-1-tadilhusrev@gmail.com \
--to=tadilhusrev@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kauschluss@disroot.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=y.oudjana@protonmail.com \
/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