Devicetree
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Wesley Cheng <quic_wcheng@quicinc.com>,
	 Bjorn Andersson <andersson@kernel.org>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	Bryan O'Donoghue <bod@kernel.org>,
	 Rakesh Kota <rakesh.kota@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 devicetree@vger.kernel.org, jishnu.prakash@oss.qualcomm.com,
	 kamal.wadhwa@oss.qualcomm.com,
	Krzysztof Kozlowski <krzk@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: (subset) [PATCH v3 0/4] regulator: qcom_usb_vbus: add pm4125 VBUS regulator support
Date: Mon, 06 Jul 2026 23:35:14 +0100	[thread overview]
Message-ID: <178337731408.411051.8794219210214073166.b4-ty@b4> (raw)
In-Reply-To: <20260706-add_pm4125-vbus-reg-v3-0-999d78a87b81@oss.qualcomm.com>

On Mon, 06 Jul 2026 18:01:04 +0530, Rakesh Kota wrote:
> regulator: qcom_usb_vbus: add pm4125 VBUS regulator support
> 
> Add support for PM4125 USB VBUS regulator. Unlike PM8150B which uses
> a current-limit selector, PM4125 uses a 2-bit VBOOST voltage selector
> supporting 4.25 V, 4.5 V, 4.75 V and 5.0 V output.
> 
> 
> [...]

Applied to

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

Thanks!

[1/4] dt-bindings: regulator: qcom,usb-vbus-regulator: add qcom,pm4125-vbus-reg
      https://git.kernel.org/broonie/sound/c/a58d2e5e1c04
[2/4] regulator: qcom_usb_vbus: add register abstraction and PM8150B support
      https://git.kernel.org/broonie/sound/c/56cb4a0e8e71
[3/4] regulator: qcom_usb_vbus: add support for qcom,pm4125-vbus-reg
      https://git.kernel.org/broonie/sound/c/d37664f99ef9

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


      parent reply	other threads:[~2026-07-07 13:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 12:31 [PATCH v3 0/4] regulator: qcom_usb_vbus: add pm4125 VBUS regulator support Rakesh Kota
2026-07-06 12:31 ` [PATCH v3 1/4] dt-bindings: regulator: qcom,usb-vbus-regulator: add qcom,pm4125-vbus-reg Rakesh Kota
2026-07-06 17:24   ` Mark Brown
2026-07-06 12:31 ` [PATCH v3 2/4] regulator: qcom_usb_vbus: add register abstraction and PM8150B support Rakesh Kota
2026-07-06 13:45   ` Bryan O'Donoghue
2026-07-06 13:46     ` Mark Brown
2026-07-06 14:29   ` Dmitry Baryshkov
2026-07-06 12:31 ` [PATCH v3 3/4] regulator: qcom_usb_vbus: add support for qcom,pm4125-vbus-reg Rakesh Kota
2026-07-06 13:48   ` Bryan O'Donoghue
2026-07-06 14:29   ` Dmitry Baryshkov
2026-07-06 15:31   ` Konrad Dybcio
2026-07-06 12:31 ` [PATCH v3 4/4] arm64: dts: qcom: Fix pm4125 vbus regulator compatible and constraints Rakesh Kota
2026-07-06 13:08   ` Konrad Dybcio
2026-07-06 13:49   ` Bryan O'Donoghue
2026-07-07  8:33     ` Rakesh Kota
2026-07-07  8:38       ` Krzysztof Kozlowski
2026-07-07  9:25       ` Konrad Dybcio
2026-07-07  9:30       ` Bryan O'Donoghue
2026-07-06 14:30   ` Dmitry Baryshkov
2026-07-07 14:03   ` Krzysztof Kozlowski
2026-07-06 22:35 ` Mark Brown [this message]

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=178337731408.411051.8794219210214073166.b4-ty@b4 \
    --to=broonie@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bod@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jishnu.prakash@oss.qualcomm.com \
    --cc=kamal.wadhwa@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_wcheng@quicinc.com \
    --cc=rakesh.kota@oss.qualcomm.com \
    --cc=robh@kernel.org \
    /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