[PATCH v3 0/5] ARM: keystone: pm: switch to use generic pm domains
grygorii.strashko at ti.com
Tue Nov 4 05:41:05 PST 2014
On 10/24/2014 09:25 PM, Santosh Shilimkar wrote:
> On 10/23/2014 07:22 AM, Grygorii Strashko wrote:
>> Hi Santosh, Kevin,
>> This series switches Keystone 2 PM code to use Generic PM domains
>> instead of PM clock domains because of the lack of DT support
>> for the last.
>> It will finally allow to enable Runtime PM for Keystone 2.
>> Patch 1 was reused from .
>> RFC version of patches can be found at .
>> Changes in v3:
>> - handling of the case when !CONFIG_PM_RUNTIME has been
>> moved in PM clock framework.
>> Changes in v2:
>> - minor comments applied and rebased on top of Linux 3.18-rc1.
>> Links on previous versions:
>> v2: https://lkml.org/lkml/2014/10/20/248
>> v1: https://lkml.org/lkml/2014/9/29/382
>>  "[PATCH/RFC 0/4] of: Register clocks for Runtime PM with PM core"
>>  "[RFC PATCH 0/4] ARM: keystone: pm: switch to use generic pm domains"
>> CC: Santosh Shilimkar <ssantosh at kernel.org>
>> CC: Kevin Hilman <khilman at linaro.org>
>> CC: Ulf Hansson <ulf.hansson at linaro.org>
>> CC: Geert Uytterhoeven <geert at linux-m68k.org>
>> CC: Dmitry Torokhov <dmitry.torokhov at gmail.com>
>> Geert Uytterhoeven (1):
>> PM / clock_ops: Add pm_clk_add_clk()
>> Grygorii Strashko (4):
>> PM / clock_ops: make __pm_clk_enable more generic
>> PM / clock_ops: add and enable clocks always if !CONFIG_PM_RUNTIME
>> ARM: keystone: pm: switch to use generic pm domains
>> ARM: dts: keystone: add generic pm controller node
> You can split this series. Lets get first 3 patches sorted out as
> there have been active discussion on those. Once they get direction
> and merged then you can post the keystone ones which I will be
> happy to merge.
Sure, will do.
Sorry, for delayed reply - I was ooo last week.
More information about the linux-arm-kernel