mbox series

[v3,0/5] regulator: qcom,rpmh-regulator: Add support for pmic available on SA8155p-adp board

Message ID 20210617051712.345372-1-bhupesh.sharma@linaro.org
Headers show
Series regulator: qcom,rpmh-regulator: Add support for pmic available on SA8155p-adp board | expand

Message

Bhupesh Sharma June 17, 2021, 5:17 a.m. UTC
Changes since v2:
-----------------
- v2 series can be found here: https://lore.kernel.org/linux-arm-msm/20210615074543.26700-1-bhupesh.sharma@linaro.org/T/#m8303d27d561b30133992da88198abb78ea833e21 
- Addressed review comments from Bjorn and Mark.
- As per suggestion from Bjorn, seperated the patches in different
  patchsets (specific to each subsystem) to ease review and patch application.

Changes since v1:
-----------------
- v1 series can be found here: https://lore.kernel.org/linux-arm-msm/20210607113840.15435-1-bhupesh.sharma@linaro.org/T/#mc524fe82798d4c4fb75dd0333318955e0406ad18
- Addressed review comments from Bjorn and Vinod received on the v1
  series.

This series adds the regulator support code for SA8155p-adp board
which is based on Qualcomm snapdragon sa8155p SoC which in turn is
simiar to the sm8150 SoC. 

This board supports a new PMIC PMM8155AU.

While at it, also make some cosmetic changes to the regulator driver
and dt-bindings to make sure the compatibles are alphabetical and also
fix issues with extra comma(s) at the end of terminator line(s). 

Cc: Mark Brown <broonie@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>

Bhupesh Sharma (5):
  dt-bindings: regulator: qcom,rpmh-regulator: Arrange compatibles
    alphabetically
  dt-bindings: regulator: qcom,rpmh-regulator: Add compatible for
    SA8155p-adp board pmic
  regulator: qcom-rpmh: Cleanup terminator line commas
  regulator: qcom-rpmh: Add terminator at the end of pm7325x_vreg_data[]
    array
  regulator: qcom-rpmh: Add new regulator found on SA8155p adp board

 .../regulator/qcom,rpmh-regulator.yaml        | 17 ++---
 drivers/regulator/qcom-rpmh-regulator.c       | 62 +++++++++++++++----
 2 files changed, 59 insertions(+), 20 deletions(-)

-- 
2.31.1

Comments

Mark Brown June 21, 2021, 6:45 p.m. UTC | #1
On Thu, 17 Jun 2021 10:47:07 +0530, Bhupesh Sharma wrote:
> Changes since v2:

> -----------------

> - v2 series can be found here: https://lore.kernel.org/linux-arm-msm/20210615074543.26700-1-bhupesh.sharma@linaro.org/T/#m8303d27d561b30133992da88198abb78ea833e21

> - Addressed review comments from Bjorn and Mark.

> - As per suggestion from Bjorn, seperated the patches in different

>   patchsets (specific to each subsystem) to ease review and patch application.

> 

> [...]


Applied to

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

Thanks!

[1/5] dt-bindings: regulator: qcom,rpmh-regulator: Arrange compatibles alphabetically
      commit: 85adaac269c36d8e2e0a5de87a1dc4ec06e984f1
[2/5] dt-bindings: regulator: qcom,rpmh-regulator: Add compatible for SA8155p-adp board pmic
      commit: 66376e152303bb60d6a75328b7bc998de86f8c08
[3/5] regulator: qcom-rpmh: Cleanup terminator line commas
      commit: ba5dabf40e9143ff6c48943b76a532d5ab34d0e8
[4/5] regulator: qcom-rpmh: Add terminator at the end of pm7325x_vreg_data[] array
      commit: f26cdadad729743888eb4ac2c17eac3cf845b493
[5/5] regulator: qcom-rpmh: Add new regulator found on SA8155p adp board
      commit: 9a336ed97d00bb69547272fc7d0439802bece375

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