All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Linux PM list <linux-pm@vger.kernel.org>,
	linaro-kernel <linaro-kernel@lists.linaro.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PM / domains: Kconfig: always enable PM_RUNTIME when genpd enabled
Date: Mon, 17 Nov 2014 10:25:58 -0800	[thread overview]
Message-ID: <7hioid3cqx.fsf@deeprootsystems.com> (raw)
In-Reply-To: <6465990.KKns6W8hQE@vostro.rjw.lan> (Rafael J. Wysocki's message of "Mon, 17 Nov 2014 02:22:52 +0100")

"Rafael J. Wysocki" <rjw@rjwysocki.net> writes:

> On Saturday, November 15, 2014 01:32:01 PM Geert Uytterhoeven wrote:
>> Hi Kevin,
>> 
>> On Fri, Nov 14, 2014 at 6:36 PM, Kevin Hilman <khilman@kernel.org> wrote:
>> >> On Thu, Nov 13, 2014 at 11:28 PM, Kevin Hilman <khilman@kernel.org> wrote:
>> >>> It makes little sense to use generic power domains without runtime PM.
>> >>
>> >> Does it?
>> >> It still powers down the PM domains on system suspend (at least on my
>> >> boards ;-)
>> >
>> > Sure, but your devices are also using runtime PM, so I'm not sure how
>> > does that change my statement above?
>> 
>> I do mean with CONFIG_PM_RUNTIME turned off.
>> 
>> If PM domain support is disabled, s2ram will not power down the PM domains.
>
> But if PM_RUNTIME is enabled along with it, I don't think it will make much
> of a different, will it?
>
> Building the kernel with genpd and without PM_RUNTIME is possible today,
> but is it really useful?  To me, it only seems to make people try to
> reinvent the wheel "because PM_RUNTIME may be unset".
>
> I have to say I'm seriously considering to make PM_SLEEP select
> PM_RUNTIME too as that would make quite a few things a *lot* simpler.

Yes.  

If that were the case, we woudn't need the pm_runtime_force_* calls
either.

Kevin

  parent reply	other threads:[~2014-11-17 18:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 22:28 [PATCH] PM / Runtime: Kconfig: move ia64 dependency to arch/ia64/Kconfig Kevin Hilman
2014-11-13 22:28 ` Kevin Hilman
2014-11-13 22:28 ` Kevin Hilman
2014-11-13 22:28 ` [PATCH] PM / domains: Kconfig: always enable PM_RUNTIME when genpd enabled Kevin Hilman
2014-11-13 22:28   ` Kevin Hilman
2014-11-14  7:26   ` Ulf Hansson
2014-11-14  7:28     ` Ulf Hansson
2014-11-14 17:27     ` Kevin Hilman
2014-11-14 17:27       ` Kevin Hilman
2014-11-14 22:35       ` Rafael J. Wysocki
2014-11-14  7:29   ` Geert Uytterhoeven
2014-11-14 17:36     ` Kevin Hilman
2014-11-14 22:41       ` Rafael J. Wysocki
2014-11-15 20:54         ` Pavel Machek
2014-11-15 12:32       ` Geert Uytterhoeven
2014-11-17  1:22         ` Rafael J. Wysocki
2014-11-17  8:01           ` Geert Uytterhoeven
2014-11-17 18:25           ` Kevin Hilman [this message]
2014-11-18  0:39             ` [PATCH] PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is selected (was: Re: [PATCH] PM / domains: Kconfig: always enable PM_RUNTIME when genpd enabled) Rafael J. Wysocki
2014-11-18  3:52               ` [PATCH] PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is selected Kevin Hilman
2014-11-18  8:32                 ` Geert Uytterhoeven
2014-11-18  8:34               ` [PATCH] PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is selected (was: Re: [PATCH] PM / domains: Kconfig: always enable PM_RUNTIME when genpd enabled) Pavel Machek
2014-11-18 20:40                 ` Rafael J. Wysocki
2014-11-14  7:30 ` [PATCH] PM / Runtime: Kconfig: move ia64 dependency to arch/ia64/Kconfig Ulf Hansson
2014-11-14  7:30   ` Ulf Hansson

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=7hioid3cqx.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=grygorii.strashko@ti.com \
    --cc=len.brown@intel.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.