diff options
| author | Jason Yang <jason98166@gmail.com> | 2026-08-21 19:44:19 +0800 |
|---|---|---|
| committer | Vinod Koul <vkoul@kernel.org> | 2026-10-03 17:04:50 +0200 |
| commit | 261e84f9278f4373970471ad71479df20d82ed4c (patch) | |
| tree | 445986ec8f7eb3c893bbe72c580a8ad389e31fd0 /include/linux | |
| parent | 8c2b331e6327ead44e72e347ce405c21dd781a99 (diff) | |
| download | linux-next-261e84f9278f4373970471ad71479df20d82ed4c.tar.gz linux-next-261e84f9278f4373970471ad71479df20d82ed4c.zip | |
phy: rockchip-samsung-dcphy: Enable runtime PM at PHY core level
phy_create() only enables runtime PM on the new PHY device if the parent
already has it enabled, and this driver enables it afterwards. The PHY
device therefore never gets runtime PM, and phy_pm_runtime_get_sync()
returns -ENOTSUPP for every phy_init() and phy_power_on(). The block is
still resumed today, but only through the supplier link fw_devlink builds
from the phys phandle, which fw_devlink=off and =permissive do not.
Move devm_pm_runtime_enable() before devm_phy_create(), as done for the
sibling HDPTX PHY in commit 10ba8479f460 ("phy:
phy-rockchip-samsung-hdptx: Enable runtime PM at PHY core level").
Fixes: b2a1a2ae7818 ("phy: rockchip: Add Samsung MIPI D-/C-PHY driver")
Signed-off-by: Jason Yang <jason98166@gmail.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Link: https://patch.msgid.link/20260821-dcphy-rpm-v1-v1-1-a7db728b2539@gmail.com
Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
