From: Kevin Hilman <khilman@linaro.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Mayuresh Kulkarni <mkulkarni@nvidia.com>,
Greg KH <gregkh@linuxfoundation.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"len.brown@intel.com" <len.brown@intel.com>,
"pavel@ucw.cz" <pavel@ucw.cz>, "rjw@sisk.pl" <rjw@sisk.pl>
Subject: Re: [PATCH] PM/domains: add delayed power off capability
Date: Fri, 22 Mar 2013 09:58:04 -0700 [thread overview]
Message-ID: <87obebe5ib.fsf@linaro.org> (raw)
In-Reply-To: <20130318100714.GL18519@tbergstrom-lnx.Nvidia.com> (Peter De Schrijver's message of "Mon, 18 Mar 2013 12:07:14 +0200")
Peter De Schrijver <pdeschrijver@nvidia.com> writes:
>> > - If such a domain is going to be needed very soon in future, it makes
>> > sense to avoid its power down for at-least that much amount of time
>> > (which is what the proposed patch does).
>>
>> ...and is also what the pluggable governors inside genpd are meant to
>> allow you to do.
>>
>
> Unfortunately this is rather akward to implement in a genpd governor. The
> governor only gets called when the genpd core wants to power off a domain.
> It can then say yes or no. You could start a timer and on expiry call into
> genpd and use a flag to indicate to the governor (which will be called
> again), it should now allow the power off.
>
>> More specifically, what you said above: "if such a domain is going to be
>> needed very soon in the future" is just another way of saying it there
>> is a wakeup latency constraint. Wakeup latency constratints are
>> handled by per-device PM QoS, which can be queried by a governor
>> associated with a genpd.
>
> No. This is not a wakeup latency constraint but rather an energy breakeven
> point constraint.
OK, that makes more sense, but the way it was described in the
changelog, it sounded like a wakeup latency constraint.
Speaking of the changelog, I would suggest it be updated to describe why
the other methods proposed here would not work.
Kevin
next prev parent reply other threads:[~2013-03-22 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 8:49 [PATCH] PM/domains: add delayed power off capability Mayuresh Kulkarni
2013-03-12 13:49 ` Greg KH
2013-03-12 14:56 ` Mayuresh Kulkarni
2013-03-12 15:19 ` Greg KH
2013-03-12 15:24 ` Peter De Schrijver
2013-03-12 15:44 ` Greg KH
2013-03-13 19:27 ` Kevin Hilman
2013-03-14 8:59 ` Peter De Schrijver
2013-03-14 14:12 ` Mayuresh Kulkarni
2013-03-15 18:04 ` Kevin Hilman
2013-03-18 10:07 ` Peter De Schrijver
2013-03-22 16:58 ` Kevin Hilman [this message]
2013-03-14 14:59 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2013-03-11 15:50 Mayuresh Kulkarni
[not found] ` <1363017028-16164-1-git-send-email-mkulkarni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-11 17:47 ` Stephen Warren
2013-03-12 14:29 ` Peter De Schrijver
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=87obebe5ib.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=mkulkarni@nvidia.com \
--cc=pavel@ucw.cz \
--cc=pdeschrijver@nvidia.com \
--cc=rjw@sisk.pl \
/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).