From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: boot: dts: am4372: add operating points
Date: Fri, 8 May 2015 15:09:23 -0500 [thread overview]
Message-ID: <554D17F3.7090008@ti.com> (raw)
In-Reply-To: <1431115050-23693-1-git-send-email-balbi@ti.com>
On 05/08/2015 02:57 PM, Felipe Balbi wrote:
> By adding operating points, cpufreq-dt has a
> chance of running and doing something useful.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> ---
> arch/arm/boot/dts/am4372.dtsi | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
> index c80a3e233792..ea1db20f64fc 100644
> --- a/arch/arm/boot/dts/am4372.dtsi
> +++ b/arch/arm/boot/dts/am4372.dtsi
> @@ -38,6 +38,15 @@
> clocks = <&dpll_mpu_ck>;
> clock-names = "cpu";
>
> + operating-points = <
> + /* kHz uV */
> + 1000000 1325000 /* OPP_NITRO */
> + 800000 1260000 /* OPP_TURBO */
> + 720000 1200000 /* OPP_120 */
> + 600000 1100000 /* OPP_100 */
> + 300000 950000 /* OPP_50 */
> + >;
> +
> clock-latency = <300000>; /* From omap-cpufreq driver */
> };
> };
>
which of these OPPs need AVS? which of these are dependent on Efuse bit
dependent?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-05-08 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 19:57 [PATCH 1/2] arm: boot: dts: am4372: add operating points Felipe Balbi
2015-05-08 19:57 ` [PATCH 2/2] cpufreq: dt: allow driver to boot automatically Felipe Balbi
2015-05-08 20:16 ` Nishanth Menon
2015-05-09 2:29 ` Viresh Kumar
2015-06-16 21:40 ` Felipe Balbi
2015-06-16 22:04 ` Rafael J. Wysocki
2015-06-16 22:08 ` Felipe Balbi
2015-05-08 20:09 ` Nishanth Menon [this message]
2015-05-08 20:12 ` [PATCH 1/2] arm: boot: dts: am4372: add operating points Nishanth Menon
2015-05-08 20:24 ` Felipe Balbi
2015-05-11 0:23 ` Nishanth Menon
2015-05-11 15:19 ` Felipe Balbi
2015-05-11 16:46 ` Nishanth Menon
2015-05-11 17:02 ` Felipe Balbi
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=554D17F3.7090008@ti.com \
--to=nm@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).