From: Vinod Koul <vkoul@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
William Wu <william.wu@rock-chips.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
Igor Paunovic <royalnet026@gmail.com>,
kernel@collabora.com
Subject: Re: [PATCH v5 0/6] phy: rockchip: inno-usb2: ensure PHY is running when clock is requested
Date: Fri, 13 Nov 2026 19:16:00 +0530 [thread overview]
Message-ID: <179457756031.652128.8747150770670489287.b4-ty@kernel.org> (raw)
In-Reply-To: <20261110-phy-rockchip-inno-usb2-clock-fix-v5-0-d2e24582ab22@collabora.com>
On Tue, 10 Nov 2026 18:19:13 +0100, Sebastian Reichel wrote:
> This was noticed on RK3588 EVB1 when resuming from system suspend. This
> is technically a fix, but its unclear when the bug was introduced and
> system suspend is broken on RK3588 for quite a while and not just due
> to this problem. So I think this fix can be merged the normal way via
> linux-next.
>
> Changes in v5:
> - Link to v4: https://patch.msgid.link/20261110-phy-rockchip-inno-usb2-clock-fix-v4-0-51acc071634f@collabora.com
> - Add new patch converting 480MHz clock registration to device maanged
> clk_hw helpers instead of using legacy clock framework functions with
> open coded device managed release handlers. This is a cleanup, which
> also allows easy implementation of the next point.
> - Restore clock registration back to the original place, so that internal
> users can access it early. The clock provider registration is kept at
> the new place (after initializing the ports) to ensure the clock can
> only be requested when either more than two ports are available or the
> port already being initialized. (Sashiko)
>
> [...]
Applied, thanks!
[1/6] phy: rockchip: inno-usb2: simplify and unify PHY op debug messages
commit: dd341fe270a274f3cc9ed4218dee0e9aa25ad954
[2/6] phy: rockchip: inno-usb2: ignore regmap_write return codes
commit: d5162b71dc6ebf997a9f64dab89ffd3bf9ebcb9b
[3/6] phy: rockchip: inno-usb2: ignore reset_control return codes
commit: c855ac52ffe0df3e71943874ff28086e73e00084
[4/6] phy: rockchip: inno-usb2: use devm for 480m clock registration
commit: 02d20d92bfa81d0198b318fcfc3527fa13401dcc
[5/6] phy: rockchip: inno-usb2: move suspend handling into new function
commit: 13f67965a6a335811bcb9cac34042d4fde591d2e
[6/6] phy: rockchip: inno-usb2: move suspend handling into clock prepare/unprepare for RK3588/RK3576
commit: 6bdfbe223ed4735073c299a6645ebd3faac3f51f
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-11-13 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 17:19 Sebastian Reichel
2026-11-10 17:19 ` [PATCH v5 1/6] phy: rockchip: inno-usb2: simplify and unify PHY op debug messages Sebastian Reichel
2026-11-10 17:19 ` [PATCH v5 2/6] phy: rockchip: inno-usb2: ignore regmap_write return codes Sebastian Reichel
2026-11-10 17:19 ` [PATCH v5 3/6] phy: rockchip: inno-usb2: ignore reset_control " Sebastian Reichel
2026-11-10 17:19 ` [PATCH v5 4/6] phy: rockchip: inno-usb2: use devm for 480m clock registration Sebastian Reichel
2026-11-10 17:19 ` [PATCH v5 5/6] phy: rockchip: inno-usb2: move suspend handling into new function Sebastian Reichel
2026-11-10 17:19 ` [PATCH v5 6/6] phy: rockchip: inno-usb2: move suspend handling into clock prepare/unprepare for RK3588/RK3576 Sebastian Reichel
2026-11-12 15:46 ` [PATCH v5 0/6] phy: rockchip: inno-usb2: ensure PHY is running when clock is requested Jakob Unterwurzacher
2026-11-13 13:46 ` Vinod Koul [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=179457756031.652128.8747150770670489287.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--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=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=royalnet026@gmail.com \
--cc=sebastian.reichel@collabora.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®