From: Vinod Koul <vkoul@kernel.org>
To: kishon@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heiko@sntech.de,
Frank Wang <frawang.cn@gmail.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, william.wu@rock-chips.com,
tim.chen@rock-chips.com, Frank Wang <frank.wang@rock-chips.com>
Subject: Re: (subset) [PATCH v6 1/4] phy: rockchip: inno-usb2: convert clock management to bulk
Date: Thu, 17 Oct 2024 21:05:41 +0530 [thread overview]
Message-ID: <172917934187.288841.9418215937562601531.b4-ty@kernel.org> (raw)
In-Reply-To: <20241016073713.14133-1-frawang.cn@gmail.com>
On Wed, 16 Oct 2024 15:37:10 +0800, Frank Wang wrote:
> Since some Rockchip SoCs (e.g RK3576) have more than one clock,
> this converts the clock management from single to bulk method to
> make the driver more flexible.
>
>
Applied, thanks!
[1/4] phy: rockchip: inno-usb2: convert clock management to bulk
commit: 86e2ed4e9a9680013ec9ab7c0428c9b8c5108efe
[3/4] dt-bindings: phy: rockchip,inno-usb2phy: add rk3576
commit: 0217f4aef0b07a57086baeed9c0ac05160435a45
[4/4] phy: rockchip: inno-usb2: Add usb2 phys support for rk3576
commit: 3d7de6e870ece5a32153382df9df6fb87613335e
Best regards,
--
~Vinod
next prev parent reply other threads:[~2024-10-17 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 7:37 Frank Wang
2024-10-16 7:37 ` [PATCH v6 2/4] dt-bindings: soc: rockchip: add rk3576 usb2phy syscon Frank Wang
2024-10-16 17:28 ` Rob Herring (Arm)
2024-10-16 7:37 ` [PATCH v6 3/4] dt-bindings: phy: rockchip,inno-usb2phy: add rk3576 Frank Wang
2024-10-16 7:37 ` [PATCH v6 4/4] phy: rockchip: inno-usb2: Add usb2 phys support for rk3576 Frank Wang
2024-10-17 15:35 ` Vinod Koul [this message]
2024-10-21 15:44 ` (subset) [PATCH v6 1/4] phy: rockchip: inno-usb2: convert clock management to bulk Heiko Stuebner
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=172917934187.288841.9418215937562601531.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.wang@rock-chips.com \
--cc=frawang.cn@gmail.com \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=tim.chen@rock-chips.com \
--cc=william.wu@rock-chips.com \
/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
all inboxes | Powered by JetHome®