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>,
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
Subject: Re: [PATCH v11 1/3] mfd: axp20x: Add support for AXP313a PMIC
Date: Thu, 25 May 2023 12:42:20 +0100 [thread overview]
Message-ID: <20230525114220.GH423913@google.com> (raw)
In-Reply-To: <20230524000012.15028-2-andre.przywara@arm.com>
On Wed, 24 May 2023, Andre Przywara wrote:
> From: Martin Botka <martin.botka@somainline.org>
>
> The AXP313a is a PMIC chip produced by X-Powers, it can be connected via
> an I2C bus.
> The name AXP1530 seems to appear as well, and this is what is used in
> the BSP driver. From all we know it's the same chip, just a different
> name. However we have only seen AXP313a chips in the wild, so go with
> this name.
>
> Compared to the other AXP PMICs it's a rather simple affair: just three
> DCDC converters, three LDOs, and no battery charging support.
>
> Describe the regmap and the MFD bits, along with the registers exposed
> via I2C. Aside from the various regulators, also describe the power key
> interrupts, and adjust the shutdown handler routine to use a different
> register than the other PMICs.
> Eventually advertise the device using the new compatible string.
>
> Signed-off-by: Martin Botka <martin.botka@somainline.org>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> Reviewed-by: Chen-Yu Tsai <wens@csie.org>
> Acked-for-MFD-by: Lee Jones <lee@kernel.org>
> ---
> drivers/mfd/axp20x-i2c.c | 2 +
> drivers/mfd/axp20x.c | 78 +++++++++++++++++++++++++++++++++++++-
> include/linux/mfd/axp20x.h | 32 ++++++++++++++++
> 3 files changed, 111 insertions(+), 1 deletion(-)
Applied (pull-request pending - waiting on build tests).
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-05-25 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 0:00 [PATCH v11 0/3] regulator: Add X-Powers AXP15060/AXP313a PMIC support Andre Przywara
2023-05-24 0:00 ` [PATCH v11 1/3] mfd: axp20x: Add support for AXP313a PMIC Andre Przywara
2023-05-25 11:42 ` Lee Jones [this message]
2023-05-24 0:00 ` [PATCH v11 2/3] regulator: axp20x: Add support for AXP313a variant Andre Przywara
2023-05-24 0:00 ` [PATCH v11 3/3] regulator: axp20x: Add AXP15060 support Andre Przywara
2023-05-24 9:10 ` [PATCH v11 0/3] regulator: Add X-Powers AXP15060/AXP313a PMIC support Shengyu Qu
2023-05-24 9:12 ` Shengyu Qu
2023-06-01 19:52 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.5 merge window Lee Jones
2023-06-06 13:30 ` (subset) [PATCH v11 0/3] regulator: Add X-Powers AXP15060/AXP313a PMIC support Mark Brown
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=20230525114220.GH423913@google.com \
--to=lee@kernel.org \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=jernej.skrabec@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).