From: Lee Jones <lee@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, Chen-Yu Tsai <wens@csie.org>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Martin Botka <martin.botka@somainline.org>,
martin.botka1@gmail.com, Shengyu Qu <wiagn233@outlook.com>,
Samuel Holland <samuel@sholland.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v10 0/3] regulator: Add X-Powers AXP313a PMIC support
Date: Fri, 21 Apr 2023 08:32:14 +0100 [thread overview]
Message-ID: <20230421073214.GN996918@google.com> (raw)
In-Reply-To: <20230401001850.4988-1-andre.przywara@arm.com>
On Sat, 01 Apr 2023, Andre Przywara wrote:
> This patch series adds support for the X-Powers AXP313a PMIC, which is
> often bundled with Allwinner H616 or H313 SoCs.
> It's my turn again for this revision of the series, after Martin did
> v7 and v8.
> After some more significant changes in v9, this is fixing some nits,
> and builds on Krzysztof's patch to simplify the DT binding document
> (patch ID at the end of this email). For a complete changelog see below.
>
> Up to v5 this was speaking of the AXP1530, which seems to be some internal
> name. The chips we have seen in the wild are all labeled AXP313a, so we
> go with this name here, from now on. This is supported by the fact that
> there is an AXP313a datasheet, but none for the AXP1530.
>
> Patch 1 is the binding documentation (just the new compatible string),
> patch 2 adds the MFD bits (mostly describing the extent of the regmap),
> while patch 3 describes the actual AXP313a register definitions.
> Since this ties neatly into the existing AXP and generic regulator
> framework, the patches are indeed only structure definitions, there is
> little new code.
>
> For now we papered over this "fixed customizable" RTC-LDO regulator in the
> same way this was done before for other PMICs (AXP803, for instance), We
> think we can fix this properly with a follow-up patch, for all instances.
MFD patches applied. PR for Mark to follow.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-04-21 7:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 0:18 [PATCH v10 0/3] regulator: Add X-Powers AXP313a PMIC support Andre Przywara
2023-04-01 0:18 ` [PATCH v10 1/3] dt-bindings: mfd: x-powers,axp152: Document the AXP313a variant Andre Przywara
2023-04-01 19:22 ` Krzysztof Kozlowski
2023-04-02 6:09 ` Chen-Yu Tsai
2023-04-21 7:30 ` Lee Jones
2023-04-01 0:18 ` [PATCH v10 2/3] mfd: axp20x: Add support for AXP313a PMIC Andre Przywara
2023-04-02 6:10 ` Chen-Yu Tsai
2023-04-21 7:31 ` Lee Jones
2023-04-21 9:35 ` Shengyu Qu
2023-04-24 9:57 ` Lee Jones
2023-04-01 0:18 ` [PATCH v10 3/3] regulator: axp20x: Add support for AXP313a variant Andre Przywara
2023-04-02 6:13 ` Chen-Yu Tsai
2023-04-05 14:21 ` Lee Jones
2023-04-05 15:07 ` Mark Brown
2023-04-05 15:36 ` Lee Jones
2023-04-05 16:15 ` Mark Brown
2023-04-05 16:39 ` Lee Jones
2023-04-05 17:07 ` Mark Brown
2023-04-05 18:03 ` Lee Jones
2023-04-05 18:38 ` Mark Brown
2023-04-06 13:49 ` Mark Brown
2023-04-14 10:32 ` Andre Przywara
2023-04-19 15:49 ` Lee Jones
2023-04-19 16:39 ` Andre Przywara
2023-04-21 7:32 ` Lee Jones [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=20230421073214.GN996918@google.com \
--to=lee@kernel.org \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=martin.botka1@gmail.com \
--cc=martin.botka@somainline.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
--cc=wiagn233@outlook.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.