Changes in v2: - Address scenario, pointed out by Kishon, that runtime PM may be enabled by the phy provider driver, *after* it have called devm_phy_create() or phy_create(). The intend of this series is to simplify the runtime PM deployment in the phy core, but while doing that fixing a related problem for a Renesas SoC making use of a phy. This issue was raised by Geert Uytterhoeven and Yoshihiro Shimoda, due to a changed behaviour in the runtime PM core. The commit in question is f8817f61e821 (PM / runtime: Drop children check from __pm_runtime_set_status()). However, it turned out that the problem existed already prior this change, only that the error was printed instead of giving a WARN splat. More details about the changes are available in each change log. For additional background, please have look at the link below. https://patchwork.kernel.org/patch/10086651/ Ulf Hansson (3): phy: core: Move runtime PM reference counting to the parent device phy: core: Drop unused runtime PM APIs phy: core: Update the runtime PM section in the docs to reflect changes Documentation/phy.txt | 29 ++++++++++++---------- drivers/phy/phy-core.c | 65 +++++++------------------------------------------ include/linux/phy/phy.h | 46 +--------------------------------- 3 files changed, 26 insertions(+), 114 deletions(-) -- 2.7.4
