From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [RFC] cpufreq_get()
Date: Thu, 22 Jan 2004 21:56:20 +0100 [thread overview]
Message-ID: <20040122205620.GA8012@dominikbrodowski.de> (raw)
In-Reply-To: <20040122190649.GC25416@poupinou.org>
[-- Attachment #1.1: Type: text/plain, Size: 498 bytes --]
On Thu, Jan 22, 2004 at 08:06:49PM +0100, Ducrot Bruno wrote:
> I'm planing to add the cpufreq_get() in struct cpufreq_driver,
> but in a hardware fashion, eventually replacing the name by
> something more appropriate.
I appreciate this suggestion.
> Even for longrun, we
> can verify that the frequency is between min and max.
For ->range() drivers [I intend to rename ->setpolicy() to ->range()], we
should leave the ->get() function optional in case the speed isn't
detectable.
Dominik
[-- 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 prev parent reply other threads:[~2004-01-22 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 19:06 [RFC] cpufreq_get() Ducrot Bruno
2004-01-22 20:56 ` Dominik Brodowski [this message]
2004-01-23 10:03 ` Ducrot Bruno
2004-01-24 20:34 ` Dominik Brodowski
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=20040122205620.GA8012@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.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