linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Alex Bee <knaerzche@gmail.com>
Cc: Chris Zhong <zyw@rock-chips.com>,
	Zhang Qing <zhangqing@rock-chips.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Add RK816 PMIC support
Date: Fri, 3 May 2024 09:18:24 +0100	[thread overview]
Message-ID: <20240503081824.GI1227636@google.com> (raw)
In-Reply-To: <171472425816.1279735.1509285489643125462.b4-ty@kernel.org>

On Fri, 03 May 2024, Lee Jones wrote:

> On Tue, 16 Apr 2024 18:12:32 +0200, Alex Bee wrote:
> > This series aims to add support for Rockchip RK816 PMIC series. As per
> > datasheet it's targeted for RK3126/RK3128 (RK816-1), RK1108 (RK816-2) and
> > PX3-SE (RK816-3) but might be used for other SoCs as well. The MFD consists
> > of an integrated RTC, a GPIO controller, two 32k clock outputs, a power
> > key, 3 buck- and 6 ldo regulators, 3 regulator-switches, and charger with
> > integrated fuel gauge. Charger and fuel gauge are not part of this series.
> > Two of the switches (otg/boost) are part of the binding, but not of
> > the driver. They must only ever be enabled if no battery charging is
> > happening, but it will be enabled automatically if a battery is attached
> > and an external power source is connected. Thus that needs some
> > incorporation of a yet to be added charger driver.
> > Integration in the existing rk8xx-infrastructure was pretty straightforward
> > and only needed very little tweaking. In order to not further bloat the
> > driver(s) too much with additional `#define`s I tried to re-use existing
> > ones wherever possible.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/5] dt-bindings: mfd: Add rk816 binding
>       commit: 06dfb41b1cf8d64327e5c4391e165f466506c4f0
> [2/5] mfd: rk8xx: Add RK816 support
>       commit: e9006f81faf8e438ea83626db578610e49f31576
> [3/5] pinctrl: rk805: Add rk816 pinctrl support
>       commit: 1bd97d64b5f0c01d03ecc9473ccfcf180dbbf54a
> [4/5] regulator: rk808: Support apply_bit for rk808_set_suspend_voltage_range
>       commit: 9f4e899c286b5127e2443d50e37ee2112efbfa2c
> [5/5] regulator: rk808: Add RK816 support
>       commit: 5eb068da74a0b443fb99a89d9e5062691649c470

Submitted for build testing.

If successful, I'll follow-up with a PR.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2024-05-03  8:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 16:12 [PATCH v4 0/5] Add RK816 PMIC support Alex Bee
2024-04-16 16:12 ` [PATCH v4 1/5] dt-bindings: mfd: Add rk816 binding Alex Bee
2024-04-16 16:12 ` [PATCH v4 2/5] mfd: rk8xx: Add RK816 support Alex Bee
2024-04-16 16:12 ` [PATCH v4 3/5] pinctrl: rk805: Add rk816 pinctrl support Alex Bee
2024-04-17  8:57   ` Linus Walleij
2024-04-18 17:48     ` Alex Bee
2024-04-19 13:31   ` Linus Walleij
2024-04-16 16:12 ` [PATCH v4 4/5] regulator: rk808: Support apply_bit for rk808_set_suspend_voltage_range Alex Bee
2024-04-23  5:21   ` Mark Brown
2024-04-16 16:12 ` [PATCH v4 5/5] regulator: rk808: Add RK816 support Alex Bee
2024-04-23  5:21   ` Mark Brown
2024-05-03  8:01 ` [PATCH v4 0/5] Add RK816 PMIC support Alex Bee
2024-05-03  8:11   ` Lee Jones
2024-05-03  8:17 ` Lee Jones
2024-05-03  8:18   ` Lee Jones [this message]
2024-05-03  8:29     ` Alex Bee
2024-05-10 14:47 ` [GIT PULL] Immutable branch between MFD, Pinctrl and Regulator due for the v6.10 merge window Lee Jones

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=20240503081824.GI1227636@google.com \
    --to=lee@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=knaerzche@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=zhangqing@rock-chips.com \
    --cc=zyw@rock-chips.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).