All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Miettinen <amiettinen@nvidia.com>
To: Kevin Hilman <khilman@ti.com>
Cc: "len.brown@intel.com" <len.brown@intel.com>,
	"markgross@thegnar.org" <markgross@thegnar.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@lists.linux-foundation.org"
	<linux-pm@lists.linux-foundation.org>,
	"j-pihet@ti.com" <j-pihet@ti.com>
Subject: Re: [PATCH 0/2] RFC: CPU frequency max as PM QoS param
Date: Mon, 27 Feb 2012 16:04:00 +0100	[thread overview]
Message-ID: <4F4B9B60.6040501@nvidia.com> (raw)
In-Reply-To: <877gz8wcud.fsf@ti.com>

To the lists too..

On 02/27/2012 04:49 PM, Kevin Hilman wrote:
> mark gross <markgross@thegnar.org> writes:
>
>  >> Current QoS settings could be thought of as performance constraints
>  >> too. It's just that they determine minimum performance. Adding
>  >> constraints for maxium performance is not a big stretch in my mind.
>  >
>  > Its not a big stretch to me either. I just think its a bit of a hack
>  > and there is a bigger more interesting issue getting overlooked.
>  >
>  > Lastly why not simply make cpufreq thermal aware and talk directly to
>  > it if you even need too?
>
> In fact, making a thermal framework "cooling device" that talks directly
> to CPUfreq is already what's being done by the Linaro PMWG folks.
>
> The problem is that CPUfreq only controls the CPU frequency.
>
> There are other devices that could be scaled back to reduce heat as well
> (DSP, and especially GPU), so having a more generic per-device
> constraint interface that can cap the frequency for *any* scalable
> device is a better framework IMO.
>
> It just so happens that pm_qos is already a good per-device constraint
> framework and can easily modified to cap performance as well as request
> a minimum performance.
>
> Kevin
>

  parent reply	other threads:[~2012-02-27 15:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 12:35 [PATCH 0/2] RFC: CPU frequency max as PM QoS param Antti P Miettinen
2012-01-19 12:35 ` [PATCH 1/2] PM QoS: Add CPU frequency maximum " Antti P Miettinen
2012-01-19 12:35 ` [PATCH 2/2] cpufreq: Enforce PM QoS maximum frequency Antti P Miettinen
2012-02-16  1:06 ` [linux-pm] [PATCH 0/2] RFC: CPU frequency max as PM QoS param Kevin Hilman
2012-02-17  3:04   ` mark gross
2012-02-17  8:12     ` [linux-pm] " Valentin, Eduardo
2012-02-20 10:00       ` Antti P Miettinen
     [not found]         ` <CAGF5oy-64J3vMKvzY=NvdV-m8_wFo=NGZANF_cnVm-iq0s-wZQ@mail.gmail.com>
     [not found]           ` <20120221145632.GA2840@envy17>
     [not found]             ` <87linw5aod.fsf@ti.com>
     [not found]               ` <20120225174449.GA17141@envy17>
2012-02-27 10:17                 ` [linux-pm] " Pihet-XID, Jean
2012-02-27 11:00                   ` Antti P Miettinen
     [not found]                 ` <877gz8wcud.fsf@ti.com>
2012-02-27 15:04                   ` Antti Miettinen [this message]
2012-02-28  0:56                     ` mark gross
2012-02-28  9:37                       ` Antti P Miettinen
2012-03-04 22:46                         ` Rafael J. Wysocki
2012-03-06 12:23                           ` Antti P Miettinen
2012-03-06 14:37                             ` Dave Jones
2012-03-07  6:38                               ` Antti P Miettinen
2012-03-07 16:59                                 ` Dave Jones
2012-03-07 18:08                                   ` 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=4F4B9B60.6040501@nvidia.com \
    --to=amiettinen@nvidia.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=j-pihet@ti.com \
    --cc=khilman@ti.com \
    --cc=len.brown@intel.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=markgross@thegnar.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.