From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/7] arm/imx6: add imx6q sabrelite board support
Date: Wed, 14 Dec 2011 22:11:11 +0800 [thread overview]
Message-ID: <20111214141109.GB1700@richard-laptop> (raw)
In-Reply-To: <20111214110558.GE27267@pengutronix.de>
On Wed, Dec 14, 2011 at 12:05:58PM +0100, Sascha Hauer wrote:
> On Tue, Dec 13, 2011 at 09:33:50PM +0800, Shawn Guo wrote:
> > On Tue, Dec 13, 2011 at 08:54:01PM +0800, Richard Zhao wrote:
> > > > > + cpus {
> > > > > + cpu at 0 {
> > > > > + clock-frequency = <996000000>;
> > > > > + };
> > > >
> > > > I do not follow why we need to have cpu frequency encoded in board
> > > > level dts. To me, what frequency the cpu is capable of running at
> > > > is really soc specific thing. So putting this data in
> > > > imx6q-sabrelite.dts is kinda suggesting that imx6q soc on this
> > > > sabrelite board can run at 996000000, while on other boards like
> > > > sabreauto/arm2 can only run at other frequency. This is seems different
> > > > from what I heard from Freescale internal development team.
> > > 1G operation needs a certain external voltage condition, though we have
> > > internal regulater. Boards that don't meet the condition have to fall back
> > > to lower frequency.
> > > From software side view, I refer to Freescale software release. please see
> > > http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=blob;f=arch/arm/mach-mx6/cpu_op-mx6.c;h=30a4346282ea5c332b4c48bf6a2d644abd9f31db;hb=imx_2.6.38_11.11.01
> > >
> > > and for imx53, there' also different max freq board:
> > > http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=blob;f=arch/arm/mach-mx5/mx53_wp.c;h=a63bae42fb661c161cab99d61f4a3108305b0f55;hb=refs/heads/imx_2.6.35_11.09.01
> > >
> > > IMHO, even the board has limitations, we'd better give an option to support
> > > it if it's possible.
> > >
> > I understand all these things. What I was suggesting is this option
> > should not be provided by the dts at all.
>
> Yes. If it's not provided the cpufreq layer should either assume 800MHz
> is the highest value which is safe on all boards or it could read the
> current frequency from the hardware. If this is 1GHz this value is
> obviously safe.
Actually, you'd better not depend on uboot to setting the highest cpu freq.
At least current freescale internel uboot don't set 1G.
Thanks
Richard
>
> Sascha
>
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-12-14 14:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 6:25 [PATCH V2 0/7] imx: add imx6 sabrelite board Richard Zhao
2011-12-13 6:25 ` [PATCH V2 1/7] dts/imx: rename gpio labels to consistent with hw spec Richard Zhao
2011-12-13 9:41 ` Shawn Guo
2011-12-13 10:40 ` Richard Zhao
2011-12-13 6:25 ` [PATCH V2 2/7] arm/imx6: add imx6q sabrelite board support Richard Zhao
2011-12-13 11:56 ` Shawn Guo
2011-12-13 12:54 ` Richard Zhao
2011-12-13 13:33 ` Shawn Guo
2011-12-14 11:05 ` Sascha Hauer
2011-12-14 14:11 ` Richard Zhao [this message]
2011-12-13 6:25 ` [PATCH V2 3/7] arm/imx: cpufreq: add multi-core support Richard Zhao
2011-12-13 6:25 ` [PATCH V2 4/7] arm/imx: fix cpufreq section mismatch Richard Zhao
2011-12-14 0:47 ` Richard Zhao
2011-12-13 6:25 ` [PATCH V2 5/7] arm/imx: add cpu_voltage to cpu_op Richard Zhao
2011-12-13 6:25 ` [PATCH V2 6/7] arm/imx6q: register arm_clk as cpu_clk to clkdev Richard Zhao
2011-12-13 6:25 ` [PATCH V2 7/7] arm/imx6q: add cpufreq support Richard Zhao
2011-12-13 10:23 ` Sascha Hauer
2011-12-13 10:38 ` Richard Zhao
2011-12-13 19:04 ` Rob Lee
2011-12-14 1:29 ` Richard Zhao
2011-12-13 12:19 ` Shawn Guo
2011-12-13 14:20 ` Sascha Hauer
2011-12-13 15:01 ` Richard Zhao
2011-12-13 8:24 ` [PATCH 1/1] arm/imx6q-sabrelite: add enet phy ksz9021rn fixup Richard Zhao
2011-12-13 12:07 ` Shawn Guo
2011-12-13 12:13 ` Richard Zhao
2011-12-13 12:47 ` Shawn Guo
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=20111214141109.GB1700@richard-laptop \
--to=richard.zhao@linaro.org \
--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