From: "André Draszik" <andre.draszik@linaro.org>
To: t.antoine@uclouvain.be
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 0/2] MAX77759 Fuel Gauge driver support
Date: Tue, 06 Jan 2026 07:12:52 +0000 [thread overview]
Message-ID: <8385a4fbb6c10cfe643c2f310f6a67150e260cf4.camel@linaro.org> (raw)
In-Reply-To: <20250915-b4-gs101_max77759_fg-v6-0-31d08581500f@uclouvain.be>
Hi Thomas,
On Mon, 2025-09-15 at 12:14 +0200, Thomas Antoine via B4 Relay wrote:
> The gs101-oriole (Google Pixel 6) and gs101-raven (Google Pixel 6 Pro)
> have a Maxim MAX77759 which provides a fuel gauge functionality based
> on the MAX M5 fuel gauge.
>
> Add a driver for the fuel gauge of the Maxim MAX77759 based on the
> one for the Maxim MAX1720x which also uses the MAX M5 fuel gauge.
>
> A future patch will add both gs101-oriole and gs101-raven as clients.
>
> Signed-off-by: Thomas Antoine <t.antoine@uclouvain.be>
Are you still working on this? Are you planning to send out a new version?
Kind Regards,
Andre'
next prev parent reply other threads:[~2026-01-06 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 10:14 [PATCH v6 0/2] MAX77759 Fuel Gauge driver support Thomas Antoine via B4 Relay
2025-09-15 10:14 ` [PATCH v6 1/2] power: supply: add support for MAX77759 fuel gauge Thomas Antoine via B4 Relay
2025-09-16 16:51 ` Sebastian Reichel
2025-09-15 10:14 ` [PATCH v6 2/2] dt-bindings: " Thomas Antoine via B4 Relay
2025-09-15 17:31 ` Conor Dooley
2025-09-18 12:36 ` Thomas Antoine
2025-09-18 13:02 ` André Draszik
2025-09-18 14:51 ` Conor Dooley
2025-09-18 22:32 ` Sebastian Reichel
2025-09-19 13:17 ` André Draszik
2026-01-27 12:22 ` Thomas Antoine
2026-01-06 7:12 ` André Draszik [this message]
2026-01-06 16:54 ` [PATCH v6 0/2] MAX77759 Fuel Gauge driver support Thomas Antoine
2026-01-06 17:08 ` André Draszik
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=8385a4fbb6c10cfe643c2f310f6a67150e260cf4.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=t.antoine@uclouvain.be \
/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