From: Fabio Estevam <festevam@gmail.com>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-pm@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Dong Aisheng <aisheng.dong@nxp.com>, Ping Bai <ping.bai@nxp.com>,
viresh kumar <viresh.kumar@linaro.org>,
rjw@rjwysocki.net,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: imx6ul: add 696MHz operating point
Date: Tue, 2 Jan 2018 13:03:03 -0200 [thread overview]
Message-ID: <CAOMZO5C-qgyCJPBHYwjD9zjHqu4eoGDfoB5-BcFdnvSy01MKiQ@mail.gmail.com> (raw)
In-Reply-To: <1514912859-17691-1-git-send-email-Anson.Huang@nxp.com>
Hi Anson,
On Tue, Jan 2, 2018 at 3:07 PM, Anson Huang <Anson.Huang@nxp.com> wrote:
> Add 696MHz operating point according to datasheet
> (Rev. 0, 12/2015).
There is a newer version from 05/2017:
https://www.nxp.com/docs/en/data-sheet/IMX6ULAEC.pdf
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> arch/arm/boot/dts/imx6ul.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6ul.dtsi b/arch/arm/boot/dts/imx6ul.dtsi
> index e0b4a46..86b3251 100644
> --- a/arch/arm/boot/dts/imx6ul.dtsi
> +++ b/arch/arm/boot/dts/imx6ul.dtsi
> @@ -68,12 +68,14 @@
> clock-latency = <61036>; /* two CLK32 periods */
> operating-points = <
> /* kHz uV */
> + 696000 1275000
> 528000 1175000
> 396000 1025000
> 198000 950000
> >;
> fsl,soc-operating-points = <
> /* KHz uV */
> + 696000 1275000
Why 1.275V?
According to the datasheet, the minimum value for VDD_SOC_CAP is 1.15V
for all frequencies.
Adding 25mV of margin leads to 1.175V.
next prev parent reply other threads:[~2018-01-02 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 17:07 [PATCH 1/2] ARM: dts: imx6ul: add 696MHz operating point Anson Huang
2018-01-02 15:03 ` Fabio Estevam [this message]
[not found] ` <E5B0DB53-D0E5-430B-BBCC-EF3899C70DAE@nxp.com>
2018-01-02 15:32 ` Fabio Estevam
2018-01-03 2:09 ` Anson Huang
2018-01-02 17:07 ` [PATCH 2/2] cpufreq: imx6q: add 696MHz operating point for i.mx6ul Anson Huang
2018-01-02 14:37 ` Fabio Estevam
[not found] ` <A2F3BA8B-361A-4809-83FE-4067CD868D5B@nxp.com>
2018-01-02 15:13 ` Fabio Estevam
[not found] ` <6FFDB281-8293-4D2C-891F-B376B52EFECF@nxp.com>
2018-01-02 15:33 ` Fabio Estevam
2018-01-03 2:10 ` Anson Huang
2018-01-05 12:21 ` Rafael J. Wysocki
2018-01-06 3:05 ` Anson Huang
2018-01-07 23:34 ` Rafael J. Wysocki
2018-01-08 1:56 ` Anson Huang
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=CAOMZO5C-qgyCJPBHYwjD9zjHqu4eoGDfoB5-BcFdnvSy01MKiQ@mail.gmail.com \
--to=festevam@gmail.com \
--cc=Anson.Huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=ping.bai@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@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).