From: Mark Brown <broonie@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Biju Das <biju.das.jz@bp.renesas.com>
Cc: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: (subset) [PATCH v4 0/6] Add USB VBUS regulator for RZ/G2L
Date: Thu, 27 Jun 2024 12:17:54 +0100 [thread overview]
Message-ID: <171948707484.56488.11243036600032850483.b4-ty@kernel.org> (raw)
In-Reply-To: <20240616105402.45211-1-biju.das.jz@bp.renesas.com>
On Sun, 16 Jun 2024 11:53:52 +0100, Biju Das wrote:
> As per RZ/G2L HW manual, VBUS enable can be controlled by the VBOUT bit of
> the VBUS Control Register(VBENCTL) register in the USBPHY Control. But
> this IP is in the Reset block.
>
> Reset driver exposes this register as regmap and instantiate the USB VBUS
> regulator device. Consumers(phy device) can use regulator APIs to control
> VBUS as controlling is done in the atomic context.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[3/6] regulator: core: Add helper for allow HW access to enable/disable regulator
commit: 1cb7d29157603561af4c38535e936850ceb99f0f
[4/6] regulator: Add Renesas RZ/G2L USB VBUS regulator driver
commit: 84fbd6198766336f627ba08f073fd9970729074e
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
prev parent reply other threads:[~2024-06-27 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 10:53 [PATCH v4 0/6] Add USB VBUS regulator for RZ/G2L Biju Das
2024-06-16 10:53 ` [PATCH v4 1/6] dt-bindings: reset: renesas,rzg2l-usbphy-ctrl: Document USB VBUS regulator Biju Das
2024-06-16 13:51 ` Krzysztof Kozlowski
2024-06-16 10:53 ` [PATCH v4 2/6] reset: renesas: Add USB VBUS regulator device as child Biju Das
2024-07-03 8:20 ` Philipp Zabel
2024-06-16 10:53 ` [PATCH v4 3/6] regulator: core: Add helper for allow HW access to enable/disable regulator Biju Das
2024-07-02 13:30 ` Mark Brown
2024-07-03 9:07 ` Philipp Zabel
2024-06-16 10:53 ` [PATCH v4 4/6] regulator: Add Renesas RZ/G2L USB VBUS regulator driver Biju Das
2024-07-11 14:40 ` Geert Uytterhoeven
2024-07-11 14:57 ` Biju Das
2024-07-11 15:14 ` Geert Uytterhoeven
2024-07-12 13:45 ` Biju Das
2024-06-16 10:53 ` [PATCH v4 5/6] phy: renesas: phy-rcar-gen3-usb2: Control VBUS for RZ/G2L SoCs Biju Das
2024-07-02 11:27 ` Vinod Koul
2024-06-16 10:53 ` [PATCH v4 6/6] arm64: dts: renesas: rz-smarc: Replace fixed regulator for USB VBUS Biju Das
2024-06-20 16:37 ` [PATCH v4 0/6] Add USB VBUS regulator for RZ/G2L Vinod Koul
2024-06-20 17:11 ` Biju Das
2024-06-27 11:17 ` 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=171948707484.56488.11243036600032850483.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-phy@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=vkoul@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