From: Shawn Guo <shawnguo@kernel.org>
To: Zhi Li <lznuaa@gmail.com>
Cc: Nicolae Rosia <nicolae.rosia@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Fancy Fang <chen.fang@freescale.com>,
Frank Li <Frank.Li@freescale.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Fugang Duan <B38611@freescale.com>,
Anson Huang <b20788@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 6/8] ARM: dts: imx: add imx6ul and imx6ul evk board support
Date: Thu, 9 Jul 2015 21:42:00 +0800 [thread overview]
Message-ID: <20150709134200.GH23464@tiger> (raw)
In-Reply-To: <CAHrpEqQMtaL_ReeFP4VR2bfg_HDaQAHc0BUMB3X4KM3b23ra0A@mail.gmail.com>
On Fri, Jun 19, 2015 at 01:55:46PM -0500, Zhi Li wrote:
> On Fri, Jun 19, 2015 at 12:05 PM, Nicolae Rosia <nicolae.rosia@gmail.com> wrote:
> > Hi,
> >
> > On Fri, Jun 19, 2015 at 6:32 PM, <Frank.Li@freescale.com> wrote:
> >> From: Frank Li <Frank.Li@freescale.com>
> > [...]
> >> + cpus {
> >> + #address-cells = <1>;
> >> + #size-cells = <0>;
> >> +
> >> + cpu0: cpu@0 {
> >> + compatible = "arm,cortex-a7";
> >> + device_type = "cpu";
> >> + reg = <0>;
> >> + clock-latency = <61036>; /* two CLK32 periods */
> >> + operating-points = <
> >> + /* kHz uV */
> >> + 528000 1250000
> >> + 396000 1150000
> >> + 198000 1150000
> >> + >;
> >> + fsl,soc-operating-points = <
> >> + /* KHz uV */
> >> + 528000 1250000
> >> + 396000 1150000
> >> + 198000 1150000
> >> + >;
> > Why is this necessary? Can't you adapt the driver to use operating-points?
> > I have looked through other imx dts and saw that some had different
> > values in these two tables.
>
> It is used by internal busfreq driver. I will remove it at next version.
It's used by mainline imx6q-cpufreq driver, but it's a piece of
undocumented binding. Basically, on i.MX6 series, when CPU frequency
scales, there are two voltages, 'core' and 'soc', need to scale
accordingly. The OPP binding v1 only supports one voltage.
Shawn
next prev parent reply other threads:[~2015-07-09 13:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 15:32 [PATCH v2 0/8] add basic support for i.mx6 ul chip Frank.Li
2015-06-19 15:32 ` [PATCH v2 1/8] ARM: imx: add i.mx6ul msl support Frank.Li
2015-06-19 15:32 ` [PATCH v2 2/8] ARM: imx: add imx6ul clk tree support Frank.Li
2015-06-19 15:32 ` [PATCH v2 3/8] Document: dt: binding: imx: update document for imx6ul support Frank.Li
2015-07-13 20:35 ` Linus Walleij
2015-06-19 15:32 ` [PATCH v2 4/8] ARM: pinctrl: imx: add i.mx6ul pinctrl driver Frank.Li
[not found] ` <1434727951-4852-5-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-07-13 20:38 ` Linus Walleij
[not found] ` <CACRpkdYszNKQqFuRrSqW0qmBp1ONO0vztG6e9LzKpG6f-_joJQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-13 20:50 ` Zhi Li
2015-07-13 20:52 ` Zhi Li
2015-07-14 7:51 ` Linus Walleij
2015-06-19 15:32 ` [PATCH v2 6/8] ARM: dts: imx: add imx6ul and imx6ul evk board support Frank.Li
2015-06-19 17:05 ` Nicolae Rosia
2015-06-19 18:55 ` Zhi Li
2015-07-09 13:42 ` Shawn Guo [this message]
2015-06-19 15:32 ` [PATCH v2 7/8] ARM: imx: imx_v6_v7_defconfig enable imx6ul support Frank.Li
2015-06-19 15:32 ` [PATCH v2 8/8] ARM: imx: add low-level debug support for i.mx6ul Frank.Li
2015-06-19 16:43 ` [PATCH v2 0/8] add basic support for i.mx6 ul chip Nicolae Rosia
2015-06-19 16:50 ` Zhi Li
[not found] ` <1434727951-4852-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-06-19 15:32 ` [PATCH v2 5/8] ARM: dts: add i.mx6ul pin function include file Frank.Li-KZfg59tc24xl57MIdRCFDg
[not found] ` <1434727951-4852-6-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-07-13 20:40 ` Linus Walleij
2015-07-14 1:16 ` Shawn Guo
2015-07-14 7:53 ` Linus Walleij
2015-07-06 19:51 ` [PATCH v2 0/8] add basic support for i.mx6 ul chip Zhi Li
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=20150709134200.GH23464@tiger \
--to=shawnguo@kernel.org \
--cc=B38611@freescale.com \
--cc=Frank.Li@freescale.com \
--cc=b20788@freescale.com \
--cc=chen.fang@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=nicolae.rosia@gmail.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).