[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1513718551-28624-1-git-send-email-ulf.hansson@linaro.org>
Date: Tue, 19 Dec 2017 22:22:28 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Kishon Vijay Abraham I <kishon@...com>,
linux-kernel@...r.kernel.org
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>, linux-pm@...r.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-renesas-soc@...r.kernel.org,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: [PATCH 0/3] phy: core: Re-work runtime PM deployment and fix an issue
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 | 28 +++++++-------
drivers/phy/phy-core.c | 99 +++++++------------------------------------------
include/linux/phy/phy.h | 45 ----------------------
3 files changed, 28 insertions(+), 144 deletions(-)
--
2.7.4
Powered by blists - more mailing lists