From: Dominik Brodowski <linux@brodo.de>
To: davej@codemonkey.org.uk, cpufreq@www.linux.org.uk
Subject: [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds
Date: Tue, 4 Nov 2003 17:08:16 +0100 [thread overview]
Message-ID: <20031104160816.GA9187@brodo.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 720 bytes --]
All drivers [davej, can you please verify for powernow-k7?] set the
transition_latency time in microseconds, even though the core demanded
nanoseconds. Instead of fixing up the drivers, fix up the core...
Dominik
diff -ruN linux-original/include/linux/cpufreq.h linux/include/linux/cpufreq.h
--- linux-original/include/linux/cpufreq.h 2003-11-04 15:27:38.000000000 +0100
+++ linux/include/linux/cpufreq.h 2003-11-04 16:09:23.547389216 +0100
@@ -57,7 +57,7 @@
struct cpufreq_cpuinfo {
unsigned int max_freq;
unsigned int min_freq;
- unsigned int transition_latency; /* in 10^(-9) s */
+ unsigned int transition_latency; /* in 10^(-6) s = microseconds */
};
struct cpufreq_real_policy {
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next reply other threads:[~2003-11-04 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 16:08 Dominik Brodowski [this message]
2003-11-10 16:32 ` [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds Dave Jones
2003-11-10 17:15 ` Ducrot Bruno
2003-11-10 17:22 ` Dave Jones
2003-11-10 20:50 ` Dominik Brodowski
2003-11-10 21:16 ` Dave Jones
2003-11-11 18:54 ` Dominik Brodowski
2003-11-11 22:45 ` Dave Jones
2003-11-12 11:01 ` Ducrot Bruno
2003-11-12 14:17 ` Dave Jones
2003-11-12 15:02 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 19:57 Pallipadi, Venkatesh
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=20031104160816.GA9187@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@codemonkey.org.uk \
/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.