From: Ducrot Bruno <ducrot@poupinou.org>
To: cpufreq@www.linux.org.uk
Subject: Re: [RFC] cpufreq_get()
Date: Fri, 23 Jan 2004 11:03:34 +0100 [thread overview]
Message-ID: <20040123100334.GD25416@poupinou.org> (raw)
In-Reply-To: <20040122205620.GA8012@dominikbrodowski.de>
On Thu, Jan 22, 2004 at 09:56:20PM +0100, Dominik Brodowski wrote:
> 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.
Fine.
>
> > 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.
Anyway, this must be optional because the ACPI performance driver can't
detect speed...
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-23 10:03 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
2004-01-23 10:03 ` Ducrot Bruno [this message]
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=20040123100334.GD25416@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox