From: Conor Dooley <conor@kernel.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>,
"André Draszik" <andre.draszik@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/2] dt-bindings: power: supply: add support for MAX77759 fuel gauge
Date: Mon, 15 Sep 2025 18:31:11 +0100 [thread overview]
Message-ID: <20250915-presoak-answering-2df6fca532ad@spud> (raw)
In-Reply-To: <20250915-b4-gs101_max77759_fg-v6-2-31d08581500f@uclouvain.be>
[-- Attachment #1: Type: text/plain, Size: 3936 bytes --]
On Mon, Sep 15, 2025 at 12:14:11PM +0200, Thomas Antoine via B4 Relay wrote:
> From: Thomas Antoine <t.antoine@uclouvain.be>
>
> The Maxim MAX77759 is a companion PMIC for USB Type-C. It contains
> Battery Charger, Fuel Gauge, temperature sensors, USB Type-C Port
> Controller (TCPC), NVMEM, and additional GPIO interfaces
>
> Use max77759-fg compatible to avoid conflict with drivers for other
> functions.
>
> The battery node is used to pass the REPCAP and ICHGTERM values
> needed for the initialization of the fuel gauge.
>
> The nvmem cells are used to get initialization values and to backup
> the learning and the number of cycles. It should work out of the box
> with gs101-oriole and gs101-raven which were previously running
> Android.
>
> Signed-off-by: Thomas Antoine <t.antoine@uclouvain.be>
> ---
> .../bindings/power/supply/maxim,max77759.yaml | 78 ++++++++++++++++++++++
> 1 file changed, 78 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/power/supply/maxim,max77759.yaml b/Documentation/devicetree/bindings/power/supply/maxim,max77759.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..4d45739fcaf26273ec57b60049d6d0421df38efb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/supply/maxim,max77759.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/supply/maxim,max77759.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Maxim Integrated MAX77759 fuel gauge
> +
> +maintainers:
> + - Thomas Antoine <t.antoine@uclouvain.be>
> +
> +allOf:
> + - $ref: power-supply.yaml#
> +
> +properties:
> + compatible:
> + const: maxim,max77759-fg
Compatible doesn't match the filename, why?
I assume the "fg" is fuel-gauge, but can this device be anything else?
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + shunt-resistor-micro-ohms:
> + description: The value of the current sense resistor in microohms.
> +
> + monitored-battery:
> + description: |
> + The fuel gauge needs the following battery properties:
> + - charge-full-design-microamp-hours
> + - charge-term-current-microamp
> +
> + nvmem-cells:
> + maxItems: 1
> + description: |
> + Saved fuel gauge state. This state will be used during the initialization
> + and saved on exit. It must be initialized beforehand.
> + Its layout must be composed of
> + - RCOMP0 (characterization of the open-circuit voltage)
> + - TCOMPO (temperature compensation information)
> + - FULLCAPREP (reported full capacity)
> + - QRTABLE00, QRTABLE10, QRTABLE20, QRTABLE30 (cell capacity information)
> + - cv_mixcap (remaining capacity of the cell without empty compensation)
> + - cv_halftime (time-to-full characterization time constant)
> + They must all be aligned on 2 bytes. A valid CRC8 checksum must
> + also be found at the end (polynomial x^8 + x^2 + x + 1).
> +
> + nvmem-cell-names:
> + const: fg_state
> +
> +required:
> + - compatible
> + - reg
> + - shunt-resistor-micro-ohms
> + - monitored-battery
> + - nvmem-cells
> + - nvmem-cell-names
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + fuel-gauge@36 {
> + compatible = "maxim,max77759-fg";
> + reg = <0x36>;
> + interrupts-extended = <&gpa9 3 IRQ_TYPE_LEVEL_LOW>;
> + shunt-resistor-micro-ohms = <5000>;
> + monitored-battery = <&battery>;
> + nvmem-cells = <&fg_state>;
> + nvmem-cell-names = "fg_state";
> + };
> + };
>
> --
> 2.51.0
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-15 17:31 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 [this message]
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 ` [PATCH v6 0/2] MAX77759 Fuel Gauge driver support André Draszik
2026-01-06 16:54 ` 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=20250915-presoak-answering-2df6fca532ad@spud \
--to=conor@kernel.org \
--cc=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