mbox series

[0/4] regulator: fix pm8009 bindings on sm8250

Message ID 20201231122348.637917-1-dmitry.baryshkov@linaro.org
Headers show
Series regulator: fix pm8009 bindings on sm8250 | expand

Message

Dmitry Baryshkov Dec. 31, 2020, 12:23 p.m. UTC 
PM8009 has special revision (P=1), which is to be used for sm8250
platform. The major difference is the S2 regulator which supplies 0.95 V
instead of 2.848V. Declare regulators data to be used for this chip
revision. The datasheet calls the chip just pm8009-1, so use the same
name.

Comments

Mark Brown Jan. 4, 2021, 5:40 p.m. UTC | #1 
On Thu, 31 Dec 2020 15:23:44 +0300, Dmitry Baryshkov wrote:
> PM8009 has special revision (P=1), which is to be used for sm8250

> platform. The major difference is the S2 regulator which supplies 0.95 V

> instead of 2.848V. Declare regulators data to be used for this chip

> revision. The datasheet calls the chip just pm8009-1, so use the same

> name.


Applied to

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

Thanks!

[1/4] dt-bindings: regulator: qcom,rpmh-regulator: add pm8009 revision
      commit: 2bf3a72b08e7f6356a2db9e1571ca65f683510bb
[2/4] regulator: qcom-rpmh-regulator: correct hfsmps515 definition
      commit: df6b92fa40050e59ea89784294bf6d04c0c47705
[3/4] regulator: qcom-rpmh-regulator: add pm8009-1 chip revision
      commit: 951384cabc5dfb09251d440dbc26058eba86f97e
[4/4] arm64: dts: qcom: qrb5165-rb5: fix pm8009 regulators
      commit: c3da02421230639bf6ee5462b70b58f5b7f3b7c6

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