[PATCH v2 0/7] Add support for the X-Powers AXP2101 PMIC

From: Olivier Louvignes

Date: Sun Nov 15 2026 - 12:12:04 EST


This adds the AXP2101 to the axp20x drivers: the MFD core with its
registers and interrupts, the regulators, the USB power supply and the
battery charger. The PMIC is on the HiBy R1, a music player built on an
Ingenic X1600. It follows how the AXP717 was added: the existing
drivers are extended, and the two power supplies get their own
compatibles because their registers differ.

Not handled yet: the PMIC's own fuel gauge (the R1 uses a CW2015, and the
AXP2101's reads 0% without a battery model), the power key, the ADC
channels, the TS pin, and writing the input current limit.

Sources: there is no datasheet behind this. The register map comes from
the GPL-2.0 AXP2101 driver of the hiby-custom-kernel project
(github.com/Jepl4r/hiby-custom-kernel), an open replacement for HiBy's
closed module, and was checked against the chip on a running R1.

Tested on the R1, on v7.3 with out-of-tree board patches:
- The rails the stock firmware turns on (DCDC1-4 at 3.3, 1.1, 1.8 and
1.2 V, ALDO2 3.3 V, ALDO3 1.1 V, ALDO4 3.3 V, BLDO1 and BLDO2 2.8 V)
read back at their stock voltages, and the regulator registers
0x80-0x9a stay byte for byte as the stock firmware left them. No
voltage was changed from Linux. BLDO1 and BLDO2 (2.8 V, the LCD
supplies) are switched on and off from Linux by the panel driver, which
claims them: bits 4 and 5 of register 0x90 clear and set again with
the screen blanking and unblanking, about 20 cycles over 8 boots, with
the selectors (0x96 and 0x97) staying at 0x17. That does not change a
voltage, since the registers already held 2.8 V. DCDC5, ALDO1, DLDO1-2
and CPUSLDO are off on the R1 and only come from the register map.
- "poweroff -f" turns the R1 off, through COMM_CFG.
- Unplugging and replugging USB gives one VBUS_REMOVAL and one
VBUS_PLUGIN interrupt, and the USB supply goes online 1, 0, 1.
- The charger registers read back as the stock firmware's values after
boot, and the battery status is Full on USB, Discharging unplugged and
Charging after a replug.

The series is on for-mfd-next (c92739a23a80, after v7.4-rc1), builds
with W=1, passes checkpatch --strict, and the three bindings pass
dt_binding_check.

Open questions: whether extending the axp20x drivers is what you want
here (the alternative is a driver of its own), and whether programming
the charger from the monitored battery at probe, read-only afterwards,
is acceptable for the battery supply.

Changes since v1:
- mfd binding: axp2101 placed by the order each allOf list already
follows (Krzysztof).
- usb-power binding: the AXP2101's input-current-limit-microamp
constrained to the six values it has (Krzysztof, and the Sashiko
review).
- mfd: axp2101_cells is const (Sashiko review).
- Acked-by from Mark Brown on the regulator patch and from Krzysztof on
the battery binding.
- Rebased on for-mfd-next after v7.4-rc1; no change to the code.

v1: https://lore.kernel.org/all/20261023100401.67592-1-olivier@xxxxxxxxx/


Olivier Louvignes (7):
dt-bindings: mfd: x-powers,axp152: Add the AXP2101
mfd: axp20x: Add support for the AXP2101
regulator: axp20x: Add support for the AXP2101
dt-bindings: power: supply: axp20x-usb-power: Add the AXP2101
power: supply: axp20x_usb_power: Add support for the AXP2101
dt-bindings: power: supply: axp20x-battery: Add the AXP2101
power: supply: axp20x_battery: Add support for the AXP2101

.../bindings/mfd/x-powers,axp152.yaml | 3 +
.../x-powers,axp20x-battery-power-supply.yaml | 1 +
.../x-powers,axp20x-usb-power-supply.yaml | 12 +
drivers/mfd/axp20x-i2c.c | 2 +
drivers/mfd/axp20x.c | 107 ++++++++-
drivers/power/supply/axp20x_battery.c | 221 ++++++++++++++++++
drivers/power/supply/axp20x_usb_power.c | 86 +++++++
drivers/regulator/axp20x-regulator.c | 88 +++++++
include/linux/mfd/axp20x.h | 114 +++++++++
9 files changed, 632 insertions(+), 2 deletions(-)


base-commit: c92739a23a80f5f0a7c6f3c10aa792102d252ac4
--
2.54.0