All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <icampbell@arcom.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] CPUFreq Support for PXA255
Date: Mon, 18 Jul 2005 12:02:06 +0100	[thread overview]
Message-ID: <1121684526.4215.25.camel@icampbell-debian> (raw)
In-Reply-To: <20050715164115.GA3240@isilmar.linta.de>

On Fri, 2005-07-15 at 18:41 +0200, Dominik Brodowski wrote:

Thanks for you comments. 

I've snipped the bits for changes that I've already done.

> > +static void pxa_select_freq_table(struct cpufreq_policy *policy,
> > +                               pxa_freqs_t ** settings,
> > +                               struct cpufreq_frequency_table
> **table)
> > +{
> [SNIP]
> > +}
> 
> As noted by Eric Piel already, please use a module parameter combined
> with a sysfs file instead.
> 
I've got it working with a module parameter so cpu_pxa.performance=1
allows selection of the performance table at boot time. 

This also creates /sys/module/cpu_pxa/parameters/performance which can
be written to and takes effect on the next frequency change. Is this
acceptable or should I look for a way to add a sysfs file
to /sys/devices/system/cpu/cpu0/cpufreq? The advantage would be
immediate application of the change (I think...)

> > +	cpumask_t cpus_allowed;
> 
> Is this a SMP-capable platform?

I don't really know to be honest -- there are SMP ARM's in the world but
I don't know if that will ever extend to the PXA. I doubt it, but I've
asked on the ARM kernel list.

> Is the PXA just a sub-architecture of ARM?

That's right, it's one of Intel's ARM implementations, it takes over
from their StrongARM stuff. The PXA line is quite commonly found in
PDAs.

> >  choice
> >  	prompt "Default CPUFreq governor"
> > -	default CPU_FREQ_DEFAULT_GOV_USERSPACE if CPU_FREQ_SA1100 || CPU_FREQ_SA1110
> > +	default CPU_FREQ_DEFAULT_GOV_USERSPACE if CPU_FREQ_SA1100 || CPU_FREQ_SA1110 || CPU_FREQ_PXA
> 
> Why is that?

I've no idea -- I just copied the StrongARM stuff. My guess is that
someone decided that PERFORMANCE wasn't suitable as the default for an
"embedded" platform. I think I'll probably just drop this chunk since
you can always choose via config anyway. I've pinged the ARM list just
in case there is a more pressing reason.

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.

  reply	other threads:[~2005-07-18 11:02 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
2005-07-15 16:41 ` Dominik Brodowski
2005-07-18 11:02   ` Ian Campbell [this message]
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=1121684526.4215.25.camel@icampbell-debian \
    --to=icampbell@arcom.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=linux@dominikbrodowski.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.