On Tue, Apr 21, 2015 at 10:56 AM, Rajendra Nayak rna...@codeaurora.org wrote:
Note that the new code always has a dev_pm_domain, while the old code had
it
conditionally on CONFIG_PM.
Right, but since USE_PM_CLK_RUNTIME_OPS is actually a nop with
!CONFIG_PM, we don't really need the checks
On Tue, Apr 21, 2015 at 1:25 AM, santosh shilimkar
santosh.shilim...@oracle.com wrote:
On 4/20/2015 4:21 PM, Kevin Hilman wrote:
Rajendra Nayak rna...@codeaurora.org writes:
Most users of PM clocks do the exact same thing in runtime callbacks.
Probably because they were all copied from
On Tue, Apr 21, 2015 at 1:25 AM, santosh shilimkar
santosh.shilim...@oracle.com wrote:
On 4/20/2015 4:21 PM, Kevin Hilman wrote:
Rajendra Nayak rna...@codeaurora.org writes:
Most users of PM clocks do the exact same thing in runtime callbacks.
Probably because they were all copied from
Rajendra Nayak rna...@codeaurora.org writes:
Most users of PM clocks do the exact same thing in runtime callbacks.
Probably because they were all copied from mach-davinci. ;)
Provide default callbacks and cleanup the existing users
(keystone/davinci/omap1/sh)
Very nice cleanup, Thanks!
On 4/20/2015 4:21 PM, Kevin Hilman wrote:
Rajendra Nayak rna...@codeaurora.org writes:
Most users of PM clocks do the exact same thing in runtime callbacks.
Probably because they were all copied from mach-davinci. ;)
Yep. ;-)
Provide default callbacks and cleanup the existing users
Most users of PM clocks do the exact same thing in runtime callbacks.
Provide default callbacks and cleanup the existing users
(keystone/davinci/omap1/sh)
Rajendra Nayak (5):
PM / clock_ops: Provide default runtime ops to users
arm: keystone: remove boilerplate code and use
