lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 26 Sep 2014 08:47:34 -0700 From: Kevin Hilman <khilman@...nel.org> To: Geert Uytterhoeven <geert+renesas@...der.be> Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>, Simon Horman <horms@...ge.net.au>, Magnus Damm <magnus.damm@...il.com>, Ulf Hansson <ulf.hansson@...aro.org>, Tomasz Figa <tomasz.figa@...il.com>, Philipp Zabel <philipp.zabel@...il.com>, Grygorii Strashko <grygorii.strashko@...com>, linux-sh@...r.kernel.org, linux-pm@...r.kernel.org, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 01/13] PM / Domains: Add genpd attach/detach callbacks Geert Uytterhoeven <geert+renesas@...der.be> writes: > While a PM domain can enable PM runtime management of its devices' module > clocks by setting > > genpd->dev_ops.stop = pm_clk_suspend; > genpd->dev_ops.start = pm_clk_resume; > > this also requires registering the clocks with the pm_clk subsystem. > In the legacy case, this is handled by the platform code, after > attaching the device to its PM domain. > > When the devices are instantiated from DT, devices are attached to their > PM domains by generic code, leaving no method for the platform-specific > PM domain code to register their clocks. > > Add two callbacks, allowing a PM domain to perform platform-specific > tasks when a device is attached to or detached from a PM domain. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be> > Reviewed-by: Ulf Hansson <ulf.hansson@...aro.org> I replied to the previous RFC, but just to be thorough (and because I like this approach): Reviewed-by: Kevin Hilman <khilman@...aro.org> Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists