mbox series

[v1,0/2] Fix USB vdd info for IPQ9574

Message ID 20250205074657.4142365-1-quic_varada@quicinc.com (mailing list archive)
Headers show
Series Fix USB vdd info for IPQ9574 | expand

Message

Varadarajan Narayanan Feb. 5, 2025, 7:46 a.m. UTC 
Use correct regulator for USB phy.

For some reason, the dt-bindings [1] patch posted and Acked long
time back seems to have slipped through the cracks and hasn't
been merged. Including it along with this patch as both are
related. dt_binding_check & dtbs_check passed.

1 - https://lore.kernel.org/linux-arm-msm/170266996013.286103.17303148912355511017.robh@kernel.org/

Varadarajan Narayanan (2):
  regulator: qcom_smd: Add l2, l5 sub-node to mp5496 regulator
  arm64: dts: qcom: ipq9574: Fix USB vdd info

 .../bindings/regulator/qcom,smd-rpm-regulator.yaml    |  2 +-
 arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi      | 11 +++++++++--
 2 files changed, 10 insertions(+), 3 deletions(-)


base-commit: 40b8e93e17bff4a4e0cc129e04f9fdf5daa5397e

Comments

Mark Brown Feb. 5, 2025, 9:04 p.m. UTC | #1 
On Wed, 05 Feb 2025 13:16:55 +0530, Varadarajan Narayanan wrote:
> Use correct regulator for USB phy.
> 
> For some reason, the dt-bindings [1] patch posted and Acked long
> time back seems to have slipped through the cracks and hasn't
> been merged. Including it along with this patch as both are
> related. dt_binding_check & dtbs_check passed.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: qcom_smd: Add l2, l5 sub-node to mp5496 regulator
      commit: b0eddc21900fb44f8c5db95710479865e3700fbd

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