From: Dominik Brodowski <linux@dominikbrodowski.net>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: CPUFreq@lists.linux.org.uk, Bruno Ducrot <ducrot@poupinou.org>,
davej@redhat.com
Subject: Re: [PATCH 2.6.14] cpufreq: don't suggest speedstep-centrino for Dothan-based Celeron-M processors
Date: Sun, 4 Dec 2005 17:46:20 +0100 [thread overview]
Message-ID: <20051204164620.GA8422@isilmar.linta.de> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60067F424F@scsmsx403.amr.corp.intel.com>
Hi,
On Fri, Dec 02, 2005 at 01:19:27PM -0800, Pallipadi, Venkatesh wrote:
> I understand acpi_throttle and processor_thermal doing it. But,
> p4-clockmod, meant for cooling should actual run like acpi_throttle and
> get triggered more like throttle rather than powersaving frequency
> drivers. Right?
> Also, if throttling information is not there in ACPI, even then P4
> clockmod can potentially be used as a replacement for acpi_throttle and
> coexist with say acpi-cpufreq.
Yes, exactly. In my TODO list for cpufreq, I still have this entry:
- [core] evaluate use of > 1 drivers at one time (CPUFREQ_THROTTLING,
CPUFREQ_SCALING)
However, as I'm too busy at the moment to tackle this issue, it'd be great
if someone else could handle this one ;)
Thanks,
Dominik
next prev parent reply other threads:[~2005-12-04 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 21:19 [PATCH 2.6.14] cpufreq: don't suggest speedstep-centrino for Dothan-based Celeron-M processors Pallipadi, Venkatesh
2005-12-04 16:46 ` Dominik Brodowski [this message]
2005-12-05 11:00 ` Bruno Ducrot
2005-12-06 6:01 ` Dominik Brodowski
2005-12-06 10:03 ` Bruno Ducrot
2005-12-06 10:10 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 16:58 Pallipadi, Venkatesh
2005-12-02 19:29 ` Felix Braun
2005-12-02 21:06 ` Bruno Ducrot
2005-12-02 14:26 Pallipadi, Venkatesh
2005-12-02 14:52 ` Felix Braun
2005-12-02 15:04 ` Bruno Ducrot
2005-12-02 13:57 Felix Braun
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=20051204164620.GA8422@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=CPUFreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=ducrot@poupinou.org \
--cc=venkatesh.pallipadi@intel.com \
/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.