From: Ian Campbell <icampbell@arcom.com>
To: Eric Piel <Eric.Piel@lifl.fr>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] CPUFreq Support for PXA255
Date: Thu, 14 Jul 2005 15:11:33 +0100 [thread overview]
Message-ID: <1121350294.10537.34.camel@icampbell-debian> (raw)
In-Reply-To: <42D6696E.4080505@lifl.fr>
On Thu, 2005-07-14 at 15:32 +0200, Eric Piel wrote:
> 14.07.2005 13:40, Ian Campbell wrote/a écrit:
> > Hi,
> Hello,
>
> I don't know so much about cpufreq, so only very few comments:
> > ===================================================================
> > --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> > +++ 2.6/arch/arm/mach-pxa/cpu-pxa.c 2005-07-14 10:57:04.000000000 +0100
> > +
> > +static void pxa_select_freq_table(struct cpufreq_policy *policy,
> > + pxa_freqs_t ** settings,
> > + struct cpufreq_frequency_table **table)
> > +{
> > + if (strcmp(policy->governor->name, "performance") == 0) {
> > + if (settings)
> > + *settings = pxa255_run_freqs;
> > + if (table)
> > + *table = pxa255_run_freq_table;
> > + } else {
> > + if (settings)
> > + *settings = pxa255_turbo_freqs;
> > + if (table)
> > + *table = pxa255_turbo_freq_table;
> > + }
> > +}
> So your driver depends on a hard-coded name of a governor ? It seems
> suspicious...
I'm not entirely happy about this either, but let me explain...
The PXA255 has essentially two orthogonal sets of available frequencies,
and it is possible to get e.g. 400MHz using either one, but with
different power consumption vs performance trades.
One of the sets of frequencies is achieved by modifying the "run mode
multiplier" which costs power but gives best performance while the other
involves modifying the "turbo mode multiplier" which uses less power for
a given speed but at the cost of some performance.
So the code selects the run mode freqs for the performance governor but
turbo for the powersave governor + any others. I did it this way because
it is an embedded processor which often can run from a battery so I
figured it makes sense to select the best power consumption over
performance unless explicitly requested. I couldn't see another method
in the cpufreq framework to select between the two modes, I guess it
could be a command line or module parameter option or something.
> [snip]
Thanks for your other comments, I'll make those changes.
Ian.
--
Ian Campbell, Senior Design Engineer
Web: http://www.arcom.com
Arcom, Clifton Road, Direct: +44 (0)1223 403 465
Cambridge CB1 7EA, United Kingdom Phone: +44 (0)1223 411 200
_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end. Email to and from Arcom is automatically monitored for operational and lawful business reasons.
This message has been virus scanned by MessageLabs.
next prev parent reply other threads:[~2005-07-14 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 11:40 [PATCH] CPUFreq Support for PXA255 Ian Campbell
2005-07-14 13:32 ` Eric Piel
2005-07-14 14:11 ` Ian Campbell [this message]
2005-07-15 16:41 ` Dominik Brodowski
2005-07-18 11:02 ` Ian Campbell
2005-07-18 12:01 ` Dominik Brodowski
2005-07-18 12:11 ` Ian Campbell
2005-07-18 14:31 ` Ian Campbell
2005-07-18 15:03 ` Dominik Brodowski
2005-07-18 15:06 ` Ian Campbell
2005-07-19 10:15 ` Ian Campbell
2005-07-23 19:16 ` Dominik Brodowski
2005-07-25 11:54 ` Ian Campbell
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=1121350294.10537.34.camel@icampbell-debian \
--to=icampbell@arcom.com \
--cc=Eric.Piel@lifl.fr \
--cc=cpufreq@lists.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 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.