mbox series

[v2,0/2] RPMh Support for PM660 and PM660L

Message ID 20220920223331.150635-1-mailingradian@gmail.com (mailing list archive)
Headers show
Series RPMh Support for PM660 and PM660L | expand

Message

Richard Acayan Sept. 20, 2022, 10:33 p.m. UTC
Changes since v1:
 - properly label

This patch series introduces support for the PM660 and PM660L on the RPMh
mailbox. My initial Pixel 3a dts is not very minimal but I think that this
series is trivial enough that it can be activated in a single commit.

 .../bindings/regulator/qcom,rpmh-regulator.yaml    | 36 +++++++++++++++
 drivers/regulator/qcom-rpmh-regulator.c            | 54 ++++++++++++++++++++++
 2 files changed, 90 insertions(+)

Comments

Mark Brown Sept. 23, 2022, 5:21 p.m. UTC | #1
On Tue, 20 Sep 2022 18:33:29 -0400, Richard Acayan wrote:
> Changes since v1:
>  - properly label
> 
> This patch series introduces support for the PM660 and PM660L on the RPMh
> mailbox. My initial Pixel 3a dts is not very minimal but I think that this
> series is trivial enough that it can be activated in a single commit.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] dt-bindings: regulator: qcom,rpmh: add pm660 and pm660l pmics
      commit: 21c93a95553d0a07091ff9894f09f5bffbfd8c8a
[2/2] regulator: qcom-rpmh: add pm660 and pm660l pmics
      commit: 911ce7cf72d9c1066a52928bffedaa103290db9e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark