From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
Cc: "Benoît Cousson"
<bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: dts: OMAP5: Update CPU OPP table as per final production Manual
Date: Mon, 16 Jun 2014 05:00:15 -0700 [thread overview]
Message-ID: <20140616120014.GH17845@atomide.com> (raw)
In-Reply-To: <1402016986-12508-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
* Nishanth Menon <nm-l0cyMroinI0@public.gmane.org> [140605 18:11]:
> As per the Final production Data Manual for OMAP5432,
> SWPS050F(APRIL 2014)
>
> There are only two OPPs - 1GHz and 1.5GHz. the older OPP_LOW has been
> completely descoped. The Nominal voltages are still correct though.
> However, expectation for final production configuration is operation
> with Adaptive Body Bias (ABB) and Adaptive Voltage Scaling Class 0
> operation.
>
> There are no IDcode or version change information encoded to
> programmatically detect this and software is supposed to NOT use
> OPP_LOW(500MHz) anymore for all devices (legacy and production
> samples).
>
> Signed-off-by: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
Thanks applying into omap-for-v3.16/fixes.
Tony
> ---
> arch/arm/boot/dts/omap5.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 3bfda16..a4ed549 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -45,7 +45,6 @@
>
> operating-points = <
> /* kHz uV */
> - 500000 880000
> 1000000 1060000
> 1500000 1250000
> >;
> --
> 1.7.9.5
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: OMAP5: Update CPU OPP table as per final production Manual
Date: Mon, 16 Jun 2014 05:00:15 -0700 [thread overview]
Message-ID: <20140616120014.GH17845@atomide.com> (raw)
In-Reply-To: <1402016986-12508-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [140605 18:11]:
> As per the Final production Data Manual for OMAP5432,
> SWPS050F(APRIL 2014)
>
> There are only two OPPs - 1GHz and 1.5GHz. the older OPP_LOW has been
> completely descoped. The Nominal voltages are still correct though.
> However, expectation for final production configuration is operation
> with Adaptive Body Bias (ABB) and Adaptive Voltage Scaling Class 0
> operation.
>
> There are no IDcode or version change information encoded to
> programmatically detect this and software is supposed to NOT use
> OPP_LOW(500MHz) anymore for all devices (legacy and production
> samples).
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Thanks applying into omap-for-v3.16/fixes.
Tony
> ---
> arch/arm/boot/dts/omap5.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 3bfda16..a4ed549 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -45,7 +45,6 @@
>
> operating-points = <
> /* kHz uV */
> - 500000 880000
> 1000000 1060000
> 1500000 1250000
> >;
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2014-06-16 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 1:09 [PATCH] ARM: dts: OMAP5: Update CPU OPP table as per final production Manual Nishanth Menon
2014-06-06 1:09 ` Nishanth Menon
[not found] ` <1402016986-12508-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2014-06-16 12:00 ` Tony Lindgren [this message]
2014-06-16 12:00 ` Tony Lindgren
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=20140616120014.GH17845@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nm-l0cyMroinI0@public.gmane.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 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.