[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAFQd5C0GZ9C-pAqAdpuyxaF2xthLPY62a921nmABTbbmYtBmQ@mail.gmail.com>
Date: Wed, 28 Feb 2018 23:07:44 +0900
From: Tomasz Figa <tfiga@...omium.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Jeffy Chen <jeffy.chen@...k-chips.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Robin Murphy <robin.murphy@....com>,
Heiko Stuebner <heiko@...ech.de>,
Caesar Wang <wxt@...k-chips.com>,
Elaine Zhang <zhangqing@...k-chips.com>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH] soc: rockchip: power-domain: remove PM clocks
On Wed, Feb 28, 2018 at 10:11 PM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> Hi Tomasz,
>
> On Wed, Feb 28, 2018 at 1:49 PM, Tomasz Figa <tfiga@...omium.org> wrote:
>> On Wed, Feb 28, 2018 at 9:32 PM, Geert Uytterhoeven
>> <geert@...ux-m68k.org> wrote:
>>> On Wed, Feb 28, 2018 at 1:29 PM, Tomasz Figa <tfiga@...omium.org> wrote:
>>>> Also, how about systems where runtime PM is disabled? I think that's
>>>> one of the reasons we control the clocks explicitly in the drivers
>>>> anyway.
>>>
>>> On many platforms, Runtime PM is always enabled.
>>
>> Can we make such assumption? If so, could we just make an explicit
>> "select PM_RUNTIME" in Kconfig of the SoC?
>
> Note that the PM_RUNTIME symbol was removed in commit 464ed18ebdb6236f
> ("PM: Eliminate CONFIG_PM_RUNTIME"), in favor of plain PM.
>
> The following already select PM unconditionally:
> - ARCH_OMAP2PLUS_TYPICAL
> - ARCH_RENESAS (except EMEV2)
> - ARCH_TEGRA
> - ARCH_VEXPRESS
Thanks! Sounds like we might be able to simplify a lot of things with
doing the same for Rockchip.
Best regards,
Tomasz
Powered by blists - more mailing lists