[PATCH v5 0/6] phy: rockchip: inno-usb2: ensure PHY is running when clock is requested

Vinod Koul vkoul at kernel.org
Fri Nov 13 05:46:00 PST 2026


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





More information about the Linux-rockchip mailing list