From: Lee Jones <lee@kernel.org>
To: Karel Balej <balejk@matfyz.cz>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org,
"Duje Mihanović" <duje.mihanovic@skole.hr>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v7 3/5] regulator: add regulators driver for Marvell 88PM886 PMIC
Date: Thu, 13 Jun 2024 14:45:34 +0100 [thread overview]
Message-ID: <20240613134534.GB2561462@google.com> (raw)
In-Reply-To: <20240531175109.15599-4-balejk@matfyz.cz>
On Fri, 31 May 2024, Karel Balej wrote:
> Support the LDO and buck regulators of the Marvell 88PM886 PMIC.
>
> Signed-off-by: Karel Balej <balejk@matfyz.cz>
> ---
>
> Notes:
> v7:
> - Address Mark's feedback:
> - Drop get_current_limit op, max_uA values and thus unneeded struct
> pm886_regulator and adapt the code accordingly.
> v6:
> - Remove all definitions (now present in the header).
> v5:
> - Add remaining regulators.
> - Clean up includes.
> - Address Mark's feedback:
> - Use dedicated regmap config.
> RFC v4:
> - Initialize regulators regmap in the regulators driver.
> - Register all regulators at once.
> - Drop regulator IDs.
> - Add missing '\n' to dev_err_probe message.
> - Fix includes.
> - Add ID table.
> RFC v3:
> - Do not have a variable for each regulator -- define them all in the
> pm886_regulators array.
> - Use new regulators regmap index name.
> - Use dev_err_probe.
> RFC v2:
> - Drop of_compatible and related code.
> - Drop unused include.
> - Remove some abstraction: use only one regmap for all regulators and
> only mention 88PM886 in Kconfig description.
> - Reword commit message.
>
> drivers/regulator/88pm886-regulator.c | 392 ++++++++++++++++++++++++++
> drivers/regulator/Kconfig | 6 +
> drivers/regulator/Makefile | 1 +
> 3 files changed, 399 insertions(+)
> create mode 100644 drivers/regulator/88pm886-regulator.c
I'm fine with this set - just waiting for Mark to review.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-06-13 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 17:34 [PATCH v7 0/5] initial support for Marvell 88PM886 PMIC Karel Balej
2024-05-31 17:34 ` [PATCH v7 1/5] dt-bindings: mfd: add entry " Karel Balej
2024-05-31 17:34 ` [PATCH v7 2/5] mfd: add driver " Karel Balej
2024-05-31 17:34 ` [PATCH v7 3/5] regulator: add regulators " Karel Balej
2024-06-13 13:45 ` Lee Jones [this message]
2024-06-26 16:52 ` Mark Brown
2024-05-31 17:34 ` [PATCH v7 4/5] input: add onkey " Karel Balej
2024-05-31 17:35 ` [PATCH v7 5/5] MAINTAINERS: add myself " Karel Balej
2024-06-28 14:41 ` [PATCH v7 0/5] initial support " Lee Jones
2024-06-28 14:42 ` Lee Jones
2024-06-28 17:20 ` Karel Balej
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=20240613134534.GB2561462@google.com \
--to=lee@kernel.org \
--cc=balejk@matfyz.cz \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=duje.mihanovic@skole.hr \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).