From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] ARM: keystone: pm: switch to use generic pm domains
Date: Tue, 4 Nov 2014 15:41:05 +0200 [thread overview]
Message-ID: <5458D771.1080109@ti.com> (raw)
In-Reply-To: <544A99B2.8080507@gmail.com>
Hi Santosh,
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 [1].
>>
>> RFC version of patches can be found at [2].
>>
>> 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
>>
>> [1] "[PATCH/RFC 0/4] of: Register clocks for Runtime PM with PM core"
>> https://lkml.org/lkml/2014/4/24/1118
>>
>> [2] "[RFC PATCH 0/4] ARM: keystone: pm: switch to use generic pm domains"
>> https://lkml.org/lkml/2014/9/25/364
>>
>> CC: Santosh Shilimkar <ssantosh@kernel.org>
>> CC: Kevin Hilman <khilman@linaro.org>
>> CC: Ulf Hansson <ulf.hansson@linaro.org>
>> CC: Geert Uytterhoeven <geert@linux-m68k.org>
>> CC: Dmitry Torokhov <dmitry.torokhov@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.
regards,
-grygorii
prev parent reply other threads:[~2014-11-04 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 14:22 [PATCH v3 0/5] ARM: keystone: pm: switch to use generic pm domains Grygorii Strashko
2014-10-23 14:22 ` [PATCH v3 1/5] PM / clock_ops: Add pm_clk_add_clk() Grygorii Strashko
2014-10-23 15:49 ` Dmitry Torokhov
2014-10-23 16:18 ` Grygorii Strashko
2014-10-23 17:13 ` Dmitry Torokhov
2014-10-23 18:04 ` Grygorii Strashko
2014-10-23 14:22 ` [PATCH v3 2/5] PM / clock_ops: make __pm_clk_enable more generic Grygorii Strashko
2014-10-23 14:23 ` [PATCH v3 3/5] PM / clock_ops: add and enable clocks always if !CONFIG_PM_RUNTIME Grygorii Strashko
2014-10-23 14:23 ` [PATCH v3 4/5] ARM: keystone: pm: switch to use generic pm domains Grygorii Strashko
2014-10-23 14:23 ` [PATCH v3 5/5] ARM: dts: keystone: add generic pm controller node Grygorii Strashko
2014-10-24 18:25 ` [PATCH v3 0/5] ARM: keystone: pm: switch to use generic pm domains Santosh Shilimkar
2014-11-04 13:41 ` Grygorii Strashko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5458D771.1080109@ti.com \
--to=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).