mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Erasmus Mari Geronimo <johnerasmusmari.geronimo@analog.com>
To: <sre@kernel.org>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/2] Add LT8491 driver
Date: Thu, 29 Oct 2026 15:30:10 +0800	[thread overview]
Message-ID: <20261029073012.1498-1-johnerasmusmari.geronimo@analog.com> (raw)

The LT8491 is a buck-boost switching regulator battery charger that
implements a constant-current constant-voltage (CCCV) charging profile.

Changes since v2:
https://lore.kernel.org/all/cover.1788432152.git.johnerasmusmari.geronimo@analog.com/
 - dt-bindings: use unevaluatedProperties: false instead of
   additionalProperties: false (Conor Dooley, sashiko-bot).
 - driver: drop the <linux/mod_devicetable.h> include and use a named
   initializer for the i2c_device_id table (Uwe Kleine-König).
 - driver: use an int for ret in lt8491_get_property() so readings
   >= 0x8000 are not treated as errors (sashiko-bot).
 - driver: register the power supply with
   devm_power_supply_register() (sashiko-bot).
 - driver: poll the telemetry-active bit after triggering a telemetry
   update (sashiko-bot).
 - driver: bounds-check the temperature limits and the resistor
   configuration values before truncating them into registers
   (sashiko-bot).
 - driver: write the 16-bit resistor configuration registers as two
   byte writes, as the device has no word-write transaction.
 - driver: report current_now in microamps.
 - driver: return -ENODATA for the temperature when the chip reports
   the not-measured-yet (0x7FFF) or thermistor-disconnected (0x7777)
   values.
 - driver: minor cleanups.

Tested on a DC2703A-A-KIT evaluation board with a Raspberry Pi 4B
(6.12-based vendor kernel) with no battery connected; charging was not
tested, nor were the two special temperature values above. Build-tested
against the power-supply for-next tree.

John Erasmus Mari Geronimo (2):
  dt-bindings: power: supply: add adi,lt8491.yaml
  power: supply: add LT8491 battery charger driver

 .../bindings/power/supply/adi,lt8491.yaml     |  92 ++++
 MAINTAINERS                                   |   7 +
 drivers/power/supply/Kconfig                  |   9 +
 drivers/power/supply/Makefile                 |   1 +
 drivers/power/supply/lt8491_charger.c         | 428 ++++++++++++++++++
 5 files changed, 537 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/power/supply/adi,lt8491.yaml
 create mode 100644 drivers/power/supply/lt8491_charger.c


base-commit: f0f400459bf6a037e70768de623fff3f8920b8bb
-- 
2.34.1


             reply	other threads:[~2026-10-29  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  7:30 John Erasmus Mari Geronimo [this message]
2026-10-29  7:30 ` [PATCH v3 1/2] dt-bindings: power: supply: add adi,lt8491.yaml John Erasmus Mari Geronimo
2026-10-29  7:30 ` [PATCH v3 2/2] power: supply: add LT8491 battery charger driver John Erasmus Mari Geronimo

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=20261029073012.1498-1-johnerasmusmari.geronimo@analog.com \
    --to=johnerasmusmari.geronimo@analog.com \
    --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=robh@kernel.org \
    --cc=sre@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®