public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: "Sripathy, Vishwanath" <vishwanath.bs@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PM-WIP-OPP][PATCH] OMAP3630 PM: Update for OPP 1GHz
Date: Tue, 6 Apr 2010 10:58:16 -0500	[thread overview]
Message-ID: <4BBB5A18.4090406@ti.com> (raw)
In-Reply-To: <1270577169-8831-1-git-send-email-vishwanath.bs@ti.com>

Sripathy, Vishwanath had written, on 04/06/2010 01:06 PM, the following:
> It is found that system is not very stable with current 1GHz OPP configuration 
> (ARM@1G, IVA@880M, VDD1@1.31V) and it has been recommended to 
> use below configuration for stable 1GHz OPP. 
> (ARM@1G, IVA@800M, VDD1@1.35V).
> 
> Signed-off-by: Vishwanath BS <vishwanath.bs@ti.com>
> ---
> diff --git a/arch/arm/mach-omap2/cpufreq34xx.c b/arch/arm/mach-omap2/cpufreq34xx.c
> index c453ec5..189c42e
> --- a/arch/arm/mach-omap2/cpufreq34xx.c
> +++ b/arch/arm/mach-omap2/cpufreq34xx.c
> @@ -82,7 +82,7 @@ static struct omap_opp_def __initdata omap36xx_mpu_rate_table[] = {
>  	/* OPP3 - OPP-Turbo */
>  	OMAP_OPP_DEF(false, 800000000, 1260000),
>  	/* OPP4 - OPP-SB */
> -	OMAP_OPP_DEF(false, 1000000000, 1310000),
> +	OMAP_OPP_DEF(false, 1000000000, 1350000),
>  	/* Terminator */
>  	OMAP_OPP_DEF(0, 0, 0)
>  };
> @@ -104,7 +104,7 @@ static struct omap_opp_def __initdata omap36xx_dsp_rate_table[] = {
>  	/* OPP3 - OPP-Turbo */
>  	OMAP_OPP_DEF(false, 660000000, 1260000),
>  	/* OPP4 - OPP-SB */
> -	OMAP_OPP_DEF(false, 875000000, 1310000),
> +	OMAP_OPP_DEF(false, 800000000, 1350000),
>  	/* Terminator */
>  	OMAP_OPP_DEF(0, 0, 0)
>  };

Acked-by: Nishanth Menon <nm@ti.com>

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2010-04-06 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 18:06 [PM-WIP-OPP][PATCH] OMAP3630 PM: Update for OPP 1GHz Vishwanath BS
2010-04-06 15:58 ` Nishanth Menon [this message]
2010-04-06 18:39   ` Kevin Hilman

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=4BBB5A18.4090406@ti.com \
    --to=nm@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vishwanath.bs@ti.com \
    /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