From: mark.langsdorf@calxeda.com (Mark Langsdorf)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC V1 2/4] dts/imx6q: add cpufreq property
Date: Thu, 15 Dec 2011 12:52:03 -0600 [thread overview]
Message-ID: <4EEA41D3.9010600@calxeda.com> (raw)
In-Reply-To: <1323947798-25251-2-git-send-email-richard.zhao@linaro.org>
On 12/15/2011 05:16 AM, Richard Zhao wrote:
> Signed-off-by: Richard Zhao<richard.zhao@linaro.org>
> ---
> arch/arm/boot/dts/imx6q.dtsi | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
> index 263e8f3..9e9943b 100644
> --- a/arch/arm/boot/dts/imx6q.dtsi
> +++ b/arch/arm/boot/dts/imx6q.dtsi
> @@ -29,6 +29,8 @@
> compatible = "arm,cortex-a9";
> reg =<0>;
> next-level-cache =<&L2>;
> + cpu_freqs =<996000000 792000000 396000000 198000000>;
> + cpu_volts =<1225000 1100000 950000 850000>;
+ trans_latency =<3000>;
> };
>
> cpu at 1 {
The trans_latency value definitely needs to be defined to avoid
strange behavior in the driver.
--Mark Langsdorf
Calxeda, Inc.
next prev parent reply other threads:[~2011-12-15 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 11:16 [RFC V1 1/4] cpufreq: add arm soc generic cpufreq driver Richard Zhao
2011-12-15 11:19 ` Richard Zhao
2011-12-15 18:50 ` Mark Langsdorf
2011-12-16 3:11 ` Richard Zhao
2011-12-16 8:24 ` Russell King - ARM Linux
2011-12-16 10:18 ` Richard Zhao
[not found] ` <1323947798-25251-2-git-send-email-richard.zhao@linaro.org>
2011-12-15 11:58 ` [RFC V1 2/4] dts/imx6q: add cpufreq property Shawn Guo
2011-12-16 2:47 ` Richard Zhao
2011-12-15 18:52 ` Mark Langsdorf [this message]
2011-12-15 20:29 ` [RFC V1 1/4] cpufreq: add arm soc generic cpufreq driver Russell King - ARM Linux
2011-12-16 3:13 ` Richard Zhao
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=4EEA41D3.9010600@calxeda.com \
--to=mark.langsdorf@calxeda.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).