From: Jerome Brunet <jbrunet@baylibre.com>
To: Lee Jones <lee@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen-Yu Tsai <wens@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 0/3] regulator: Add X-Powers AXP318W PMIC support
Date: Fri, 10 Jul 2026 19:02:15 +0200 [thread overview]
Message-ID: <1jse5qg4mg.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20260710-axp318-regulator-v2-0-ee5f1c56b49f@baylibre.com> (Jerome Brunet's message of "Fri, 10 Jul 2026 18:19:24 +0200")
On ven. 10 juil. 2026 at 18:19, Jerome Brunet <jbrunet@baylibre.com> wrote:
> This patch series adds support for the X-Powers AXP318W PMIC, which is
> used recently on new boards with Allwinner SoCs (the A733).
>
> The PMIC features 9 DCDC buck converters and 28 LDOs, plus the usual ADC,
> interrupts, and power key components.
> A datasheet can be found linked in this Wiki table:
> https://linux-sunxi.org/AXP_PMICs
>
> Patch 1 adds the compatible string to the binding document, and adds
> the additional input supply properties.
> Patch 2 is the MFD part, describing the regmap and all the interrupts.
> So far we support the regulator and power key devices, the ADC and
> other pieces will follow later.
> Patch 3 adds the voltage regulator rails, this part is crucial to enable
> any board using this PMIC, as we depend on those rails even for basic
> devices.
>
> There was an unclosed topic regarding the handling of LDOs output
> voltage being limited to input voltage being provided by the supply.
> Chen-Yu noted the min_dropout_uV would be a good fit for that but
> the actual minimal dropout value was unknown. I've arbitrarily picked
> 1uV because it is the minimum the framework supports. Realistically a low
> dropout regulator is bound to have some dropout. This choice
> is very likely optimistic but does the trick for now.
>
> If anyone has problems because the dropout is actually higher
> * it is arguably an HW design error
> * it is a good time to let us know what the actual dropout is :P
>
I've focused on the regulator and the comments from v1 while taking over,
assuming the rest was fine. I should not have. Please ignore this
version. I'll re-spin it.
> Changes in v2:
> * Droped _NUM_VOLTAGES macros
> * Use min_dropout_uV to limit LDO voltage to supplies
> * Add bypass mode for EDLO4/5
> * Prevent crossing 1.54V threshold for DCDC6/7/8/9
> * Link to v1: https://lore.kernel.org/r/20251021112013.2710903-1-andre.przywara@arm.com
>
> ---
> Andre Przywara (3):
> dt-bindings: mfd: x-powers,axp152: Document AXP318W
> mfd: axp20x: Add support for AXP318W PMIC
> regulator: axp20x: add support for the AXP318W
>
> .../devicetree/bindings/mfd/x-powers,axp152.yaml | 28 +-
> drivers/mfd/axp20x-i2c.c | 2 +
> drivers/mfd/axp20x.c | 84 ++++++
> drivers/regulator/axp20x-regulator.c | 298 ++++++++++++++++++++-
> include/linux/mfd/axp20x.h | 129 +++++++++
> 5 files changed, 532 insertions(+), 9 deletions(-)
> ---
> base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
> change-id: 20260710-axp318-regulator-43545ce3261f
>
> Best regards,
--
Jerome
prev parent reply other threads:[~2026-07-10 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 16:19 [PATCH v2 0/3] regulator: Add X-Powers AXP318W PMIC support Jerome Brunet
2026-07-10 16:19 ` [PATCH v2 1/3] dt-bindings: mfd: x-powers,axp152: Document AXP318W Jerome Brunet
2026-07-10 16:30 ` sashiko-bot
2026-07-10 16:19 ` [PATCH v2 2/3] mfd: axp20x: Add support for AXP318W PMIC Jerome Brunet
2026-07-10 16:31 ` sashiko-bot
2026-07-10 16:19 ` [PATCH v2 3/3] regulator: axp20x: add support for the AXP318W Jerome Brunet
2026-07-10 16:27 ` Jerome Brunet
2026-07-10 16:29 ` sashiko-bot
2026-07-10 17:00 ` Mark Brown
2026-07-11 12:37 ` Jerome Brunet
2026-07-10 17:02 ` Jerome Brunet [this message]
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=1jse5qg4mg.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wens@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