From: Peter Chen <peter.chen@freescale.com>
To: Shawn Guo <shawn.guo@linaro.org>, b20788@freescale.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
pawel.moll@arm.com, robh+dt@kernel.org, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: imx6sx-sdb: change default board as reva board
Date: Tue, 20 Jan 2015 14:30:18 +0800 [thread overview]
Message-ID: <20150120063016.GD13645@shlinux2> (raw)
In-Reply-To: <20150120073527.GT2766@dragon>
On Tue, Jan 20, 2015 at 03:35:29PM +0800, Shawn Guo wrote:
> On Wed, Jan 14, 2015 at 03:36:37PM +0800, Peter Chen wrote:
> > The imx6sx sdb board has two revisions, the current mainline one
> > is reva which is mainly for internal use. In this commit, we
> > rename imx6sx-sdb.dts to imx6sx-sdb.dtsi, and move the reva dedicated
> > contents to imx6sx-sdb-reva.dts.
> >
> > Signed-off-by: Peter Chen <peter.chen@freescale.com>
> > ---
> > arch/arm/boot/dts/imx6sx-sdb-reva.dts | 158 +++++++++++++++++++++
> > .../boot/dts/{imx6sx-sdb.dts => imx6sx-sdb.dtsi} | 131 -----------------
>
> arch/arm/boot/dts/Makefile needs an update.
>
Thanks, I will.
> > 2 files changed, 158 insertions(+), 131 deletions(-)
> > create mode 100644 arch/arm/boot/dts/imx6sx-sdb-reva.dts
> > rename arch/arm/boot/dts/{imx6sx-sdb.dts => imx6sx-sdb.dtsi} (83%)
> >
> > diff --git a/arch/arm/boot/dts/imx6sx-sdb-reva.dts b/arch/arm/boot/dts/imx6sx-sdb-reva.dts
> > new file mode 100644
> > index 0000000..e7a8c34
> > --- /dev/null
> > +++ b/arch/arm/boot/dts/imx6sx-sdb-reva.dts
> > @@ -0,0 +1,158 @@
> > +/*
> > + * Copyright (C) 2014-2015 Freescale Semiconductor, Inc.
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > + */
> > +
> > +#include "imx6sx-sdb.dtsi"
> > +
> > +/ {
> > + model = "Freescale i.MX6 SoloX SDB RevA Board";
> > +};
> > +
> > +&cpu0 {
> > + operating-points = <
> > + /* kHz uV */
> > + 996000 1250000
> > + 792000 1175000
> > + 396000 1075000
> > + >;
> > + fsl,soc-operating-points = <
> > + /* ARM kHz SOC uV */
> > + 996000 1175000
> > + 792000 1175000
> > + 396000 1175000
> > + >;
>
> I'm wondering why different revision of the board require a different
> OPP settings.
>
Anson, do you know the reason?
Peter
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2015-01-20 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 7:36 [PATCH 0/2] ARM: imx6sx-sdb: add revb board Peter Chen
[not found] ` <1421220998-3491-1-git-send-email-peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-01-14 7:36 ` [PATCH 1/2] ARM: imx6sx-sdb: change default board as reva board Peter Chen
[not found] ` <1421220998-3491-2-git-send-email-peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-01-20 7:35 ` Shawn Guo
2015-01-20 6:30 ` Peter Chen [this message]
2015-01-20 7:51 ` Anson.Huang-KZfg59tc24xl57MIdRCFDg
[not found] ` <BN1PR0301MB062873E37C225DD38B2BCE3CFF4B0-RQSpjbwlmjRcEY/EnGXkZZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-01-20 8:03 ` Shawn Guo
2015-01-14 7:36 ` [PATCH 2/2] ARM: imx6sx-sdb: add revb board Peter Chen
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=20150120063016.GD13645@shlinux2 \
--to=peter.chen@freescale.com \
--cc=b20788@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.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).