On 10/12/2014 03:56 PM, Kevin Hilman wrote:
Hi Grygorii,
On 9/29/14 7:38 AM, Grygorii Strashko wrote:
This patch 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.
Signed-off-by: Grygorii Strashko
IMO, this appro
On 10/2/14 12:17 PM, Santosh Shilimkar wrote:
> On Monday 29 September 2014 10:38 AM, Grygorii Strashko wrote:
>> This patch 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.
>>
>> Signed-off-by: Grygorii Strashko
Hi Grygorii,
On 9/29/14 7:38 AM, Grygorii Strashko wrote:
> This patch 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.
>
> Signed-off-by: Grygorii Strashko
IMO, this approach is much better.
One minor nit belo
On Monday 29 September 2014 10:38 AM, Grygorii Strashko wrote:
> This patch 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.
>
> Signed-off-by: Grygorii Strashko
> ---
> .../devicetree/bindings/power/ti,keystone
Hi Grygorii,
On Mon, Sep 29, 2014 at 4:38 PM, Grygorii Strashko
wrote:
> This patch 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.
Thanks, this looks interesting, as today I've been digging deeper into the
!CO
This patch 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.
Signed-off-by: Grygorii Strashko
---
.../devicetree/bindings/power/ti,keystone-gpc.txt | 31 ++
arch/arm/mach-keystone/Kconfig |
6 matches
Mail list logo
