public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pxa: support 806MHz operating points for PXA31x processors A2 stepping
Date: Tue, 15 Feb 2011 18:58:04 +0200	[thread overview]
Message-ID: <4D5AB09C.9000106@compulab.co.il> (raw)
In-Reply-To: <1297786849.2596.13.camel@phoenix>

Hi,

On 02/15/11 18:20, Axel Lin wrote:

> PXA3xx Specification Update document states that the 806MHz
> operating points were added for PXA31x processors A2 stepping.
>
> This patch adds 806MHz operating points support for PXA31x A2 stepping.
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
>
> I cannot find any details for PXA31x stepping B1 and B2,
> thus I made this patch for PXA31x stepping A2 only.
>
> Axel
>
>  arch/arm/mach-pxa/cpufreq-pxa3xx.c |   23 +++++++++++++++++++----
>  1 files changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/mach-pxa/cpufreq-pxa3xx.c b/arch/arm/mach-pxa/cpufreq-pxa3xx.c
> index 88fbec0..f4f0c2e 100644
> --- a/arch/arm/mach-pxa/cpufreq-pxa3xx.c
> +++ b/arch/arm/mach-pxa/cpufreq-pxa3xx.c
> @@ -210,15 +210,30 @@ static int pxa3xx_cpufreq_init(struct cpufreq_policy *policy)
>  
>  	/* set default policy and cpuinfo */
>  	policy->cpuinfo.min_freq = 104000;
> -	policy->cpuinfo.max_freq = (cpu_is_pxa320()) ? 806000 : 624000;
> +
> +	if (cpu_is_pxa300())
> +		policy->cpuinfo.max_freq = 624000;
> +	else if (cpu_is_pxa310())
> +		policy->cpuinfo.max_freq = ((read_cpuid_id() & 0xf) == 0x2) ?
> +						806000 : 624000;
> +	else if (cpu_is_pxa320())
> +		policy->cpuinfo.max_freq = 806000;
> +
>  	policy->cpuinfo.transition_latency = 1000; /* FIXME: 1 ms, assumed */
>  	policy->max = pxa3xx_get_clk_frequency_khz(0);
>  	policy->cur = policy->min = policy->max;
>  
> -	if (cpu_is_pxa300() || cpu_is_pxa310())
> +	if (cpu_is_pxa300())
>  		ret = setup_freqs_table(policy, ARRAY_AND_SIZE(pxa300_freqs));
> -
> -	if (cpu_is_pxa320())
> +	else if (cpu_is_pxa310())
> +		/* PXA310 A2 STEPPING supports 806Mhz operating points */
> +		if ((read_cpuid_id() & 0xf) == 0x2)
> +			ret = setup_freqs_table(policy,
> +						ARRAY_AND_SIZE(pxa320_freqs));
> +		else
> +			ret = setup_freqs_table(policy,
> +						ARRAY_AND_SIZE(pxa300_freqs));
> +	else if (cpu_is_pxa320())
>  		ret = setup_freqs_table(policy, ARRAY_AND_SIZE(pxa320_freqs));
>  
>  	if (ret) {

Yeah, I've proposed something like that about half a year ago:
http://www.spinics.net/lists/arm-kernel/msg92899.html

Eric was not so happy about it back then, may be this time?
Eric, what do you think?

Also, there is one thing that is not related to this patch, but
if you have the hardware, you need to be concerned with,
is that the vcc_core voltage has to be 1.4V, otherwise your
hardware will be unstable.

-- 
Regards,
Igor.

  reply	other threads:[~2011-02-15 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 16:20 [PATCH] ARM: pxa: support 806MHz operating points for PXA31x processors A2 stepping Axel Lin
2011-02-15 16:58 ` Igor Grinberg [this message]
2011-02-22  1:12   ` Axel Lin
2011-02-22  8:35     ` Igor Grinberg
2011-02-22 10:38       ` Axel Lin
2011-02-22 13:19         ` Eric Miao
2011-02-23  1:33           ` Haojian Zhuang
2011-02-22 13:22         ` Igor Grinberg

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=4D5AB09C.9000106@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.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