From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Ryan Underwood <nemesis@icequake.net>
Cc: Cpufreq@lists.linux.org.uk, Bruno Ducrot <ducrot@poupinou.org>
Subject: Re: writing a cpufreq driver
Date: Mon, 2 Oct 2006 04:19:47 +0200 [thread overview]
Message-ID: <20061002021947.GE19253@isilmar.linta.de> (raw)
In-Reply-To: <20060925153914.GB1364@dbz.icequake.net>
On Mon, Sep 25, 2006 at 10:39:14AM -0500, Ryan Underwood wrote:
> Interesting that if it were SMI throttling, they would refer to it as
> "stop clock". I wonder if anyone can tell us whether STPCLK stops TSC
> or not.
As far as I know, the TSC is usually stopped when triggering STPCLK on an
"older" CPU. Does the battery run-time increase when you use your driver?
Then it's doing _something_ , even if we do not know what it does exactly :)
Dominik
next prev parent reply other threads:[~2006-10-02 2:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 18:48 writing a cpufreq driver Ryan Underwood
2006-09-21 19:31 ` Dave Jones
2006-09-21 19:38 ` Langsdorf, Mark
2006-09-21 19:47 ` Dave Jones
2006-09-22 15:44 ` Bruno Ducrot
2006-09-22 15:49 ` Dave Jones
2006-09-21 20:08 ` Ryan Underwood
2006-09-21 20:44 ` Dave Jones
2006-09-21 21:03 ` Ryan Underwood
2006-09-21 21:13 ` Dave Jones
2006-09-22 14:13 ` Ryan Underwood
2006-09-22 14:39 ` Ryan Underwood
2006-09-22 15:48 ` Bruno Ducrot
2006-09-22 16:01 ` Ryan Underwood
2006-09-22 15:51 ` Dave Jones
2006-09-22 15:39 ` Bruno Ducrot
2006-09-22 16:00 ` Ryan Underwood
2006-09-22 16:05 ` Bruno Ducrot
2006-09-22 16:11 ` Ryan Underwood
2006-09-23 15:07 ` Bruno Ducrot
2006-09-23 15:21 ` Ryan Underwood
2006-09-23 15:44 ` Bruno Ducrot
2006-09-23 16:03 ` Ryan Underwood
2006-09-23 16:13 ` Bruno Ducrot
2006-09-25 15:39 ` Ryan Underwood
2006-10-02 2:19 ` Dominik Brodowski [this message]
2006-09-25 16:44 ` Ryan Underwood
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 16:31 Erik Slagter
2006-09-23 15:31 ` Bruno Ducrot
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=20061002021947.GE19253@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=Cpufreq@lists.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=nemesis@icequake.net \
/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.