From: Krzysztof Kozlowski <krzk@kernel.org>
To: t.antoine@uclouvain.be, "Sebastian Reichel" <sre@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v5 4/4] arm64: dts: exynos: google: add Maxim MAX77759 Fuel-gauge
Date: Sun, 24 Aug 2025 19:14:36 +0200 [thread overview]
Message-ID: <539ede1a-eab6-4e8d-b108-11033cb39512@kernel.org> (raw)
In-Reply-To: <20250804-b4-gs101_max77759_fg-v5-4-03a40e6c0e3d@uclouvain.be>
On 04/08/2025 16:26, Thomas Antoine via B4 Relay wrote:
> From: Thomas Antoine <t.antoine@uclouvain.be>
>
> Add the node for the Maxim MAX77759 fuel gauge as a slave of the i2c.
>
> The TODO is still applicable given there are other slaves on the
> bus (e.g. PCA9468, other MAX77759 functions and the MAX20339 OVP).
>
> For the device specific values (full design capacity and terminal
> current), the device should check an EEPROM at address 0x50 of the
> hsi2c_8 for a battery id stored in register 0x17. A set of parameters
> for the initialization of the fuel gauge should be chosen based on
> this id. Those sets are defined here:
>
> Link: https://android.googlesource.com/kernel/gs/+/refs/heads/android-gs-raviole-5.10-android15/arch/arm64/boot/dts/google/gs101-oriole-battery-data.dtsi
> Link: https://android.googlesource.com/kernel/gs/+/refs/heads/android-gs-raviole-5.10-android15/arch/arm64/boot/dts/google/gs101-raven-battery-data.dtsi
>
> This does not seem to be a standard pattern in the kernel currently
> so it is not implemented. Values observed on tested devices are
> instead used. The driver or the devicetree should be should be
> extended in the future to take versions into account.
>
> The pinctrl name follows the convention proposed in
> Link: https://lore.kernel.org/all/20250524-b4-max77759-mfd-dts-v2-2-b479542eb97d@linaro.org/
>
> Signed-off-by: Thomas Antoine <t.antoine@uclouvain.be>
> ---
> arch/arm64/boot/dts/exynos/google/gs101-oriole.dts | 10 ++++++++
> .../boot/dts/exynos/google/gs101-pixel-common.dtsi | 30 ++++++++++++++++++++++
> arch/arm64/boot/dts/exynos/google/gs101-raven.dts | 11 ++++++++
> 3 files changed, 51 insertions(+)
Code looks fine, so same comment as for defconfig change.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-24 18:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 14:26 [PATCH v5 0/4] gs101: MAX77759 Fuel Gauge driver support and enablement Thomas Antoine via B4 Relay
2025-08-04 14:26 ` [PATCH v5 1/4] power: supply: add support for MAX77759 fuel gauge Thomas Antoine via B4 Relay
2025-09-06 21:22 ` Sebastian Reichel
2025-09-12 11:16 ` Peter Griffin
2025-08-04 14:26 ` [PATCH v5 2/4] dt-bindings: " Thomas Antoine via B4 Relay
2025-08-05 8:32 ` Krzysztof Kozlowski
2025-08-04 14:26 ` [PATCH v5 3/4] arm64: defconfig: enable Maxim MAX77759 fuel-gauge driver Thomas Antoine via B4 Relay
2025-08-24 17:13 ` Krzysztof Kozlowski
2025-09-12 10:40 ` Peter Griffin
2025-08-04 14:26 ` [PATCH v5 4/4] arm64: dts: exynos: google: add Maxim MAX77759 Fuel-gauge Thomas Antoine via B4 Relay
2025-08-24 17:14 ` Krzysztof Kozlowski [this message]
2025-08-25 12:25 ` André Draszik
2025-09-12 10:47 ` Peter Griffin
2025-08-05 6:20 ` [PATCH v5 0/4] gs101: MAX77759 Fuel Gauge driver support and enablement Krzysztof Kozlowski
2025-08-05 8:23 ` Thomas Antoine
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=539ede1a-eab6-4e8d-b108-11033cb39512@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=t.antoine@uclouvain.be \
--cc=tudor.ambarus@linaro.org \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®