From: Antti P Miettinen <amiettinen@nvidia.com>
To: linux-pm@lists.linux-foundation.org
Cc: cpufreq@vger.kernel.org
Subject: Re: [PATCH v2 0/8] RFC: CPU frequency min/max as PM QoS params
Date: Thu, 02 Feb 2012 08:06:38 +0200 [thread overview]
Message-ID: <87vcnp93bl.fsf@amiettinen-lnx.nvidia.com> (raw)
In-Reply-To: 201201230043.46436.rjw@sisk.pl
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Sunday, January 22, 2012, Antti P Miettinen wrote:
[..]
>> Seems that the device specific constraints are not yet in use in
>> 3.3-rc1, or am I not looking hard enough?
>
> They are in use through generic PM domains (drivers/base/power/domain*.c
> and friends) and ARM/shmobile uses those.
>
> Thanks,
> Rafael
Sorry for the delay - got pre-empted by other stuff. I took a look at
the per device constraints. Do I understand it correctly that the idea
is that there is only one constraint per device? If we want to make
frequency and latency per CPU I guess we'd need separate constraints
associated with the CPU device. Or do I misunderstand something?
Or would global CPU frequency be more in line with global CPU latency
after all?
--Antti
next prev parent reply other threads:[~2012-02-02 6:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 6:59 [PATCH v2 0/8] RFC: CPU frequency min/max as PM QoS params Antti P Miettinen
2012-01-16 6:59 ` [PATCH v2 1/8] PM QoS: Simplify PM QoS expansion/merge Antti P Miettinen
2012-01-16 21:22 ` Rafael J. Wysocki
2012-01-18 2:50 ` mark gross
2012-01-16 6:59 ` [PATCH v2 2/8] PM QoS: Add CPU frequency minimum as PM QoS param Antti P Miettinen
2012-01-16 6:59 ` [PATCH v2 3/8] cpufreq: Export user_policy min/max Antti P Miettinen
2012-01-16 6:59 ` [PATCH v2 4/8] cpufreq: Preserve sysfs min/max request Antti P Miettinen
2012-01-16 6:59 ` [PATCH v2 5/8] cpufreq: Enforce PM QoS minimum limit Antti P Miettinen
2012-01-16 6:59 ` [PATCH v2 6/8] input: CPU frequency booster Antti P Miettinen
2012-01-16 7:00 ` [PATCH v2 7/8] PM QoS: Add CPU frequency maximum as PM QoS param Antti P Miettinen
2012-01-16 7:00 ` [PATCH v2 8/8] cpufreq: Enforce PM QoS maximum frequency Antti P Miettinen
2012-01-16 21:38 ` [PATCH v2 0/8] RFC: CPU frequency min/max as PM QoS params Rafael J. Wysocki
2012-01-17 6:14 ` Antti P Miettinen
2012-01-17 6:25 ` [linux-pm] " Mansoor, Illyas
2012-01-17 9:54 ` Antti P Miettinen
2012-01-17 21:27 ` [linux-pm] " Rafael J. Wysocki
2012-01-18 7:52 ` Antti P Miettinen
2012-01-18 23:10 ` [linux-pm] " Rafael J. Wysocki
2012-01-19 6:41 ` Antti P Miettinen
2012-01-18 3:13 ` mark gross
2012-01-18 8:15 ` Antti P Miettinen
2012-01-18 23:16 ` [linux-pm] " Rafael J. Wysocki
2012-01-18 23:24 ` Rafael J. Wysocki
2012-01-19 6:49 ` Antti P Miettinen
2012-01-19 22:40 ` [linux-pm] " Rafael J. Wysocki
2012-01-22 9:55 ` Antti P Miettinen
2012-01-19 16:41 ` [linux-pm] " mark gross
2012-01-19 19:48 ` Antti P Miettinen
2012-01-19 22:15 ` [linux-pm] " Rafael J. Wysocki
2012-01-22 10:35 ` Antti P Miettinen
2012-01-22 23:43 ` [linux-pm] " Rafael J. Wysocki
2012-02-02 6:06 ` Antti P Miettinen [this message]
2012-02-08 8:49 ` Per CPU frequency constraints (was Re: [PATCH v2 0/8] RFC: CPU frequency min/max as PM QoS params) Antti P Miettinen
2012-01-19 23:36 ` [linux-pm] [PATCH v2 0/8] RFC: CPU frequency min/max as PM QoS params Rafael J. Wysocki
2012-01-18 3:44 ` mark gross
2012-01-18 20:22 ` Antti P Miettinen
[not found] <1326459559-5436-1-git-send-email-amiettinen@nvidia.com>
[not found] ` <20120113152445.GA3005@mgross-G62>
2012-01-13 16:17 ` Antti P Miettinen
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=87vcnp93bl.fsf@amiettinen-lnx.nvidia.com \
--to=amiettinen@nvidia.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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).