devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anson Huang <Anson.Huang@nxp.com>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: shawnguo@kernel.org, kernel@pengutronix.de,
	fabio.estevam@nxp.com, robh+dt@kernel.org, mark.rutland@arm.com,
	linux@armlinux.org.uk, rjw@rjwysocki.net,
	viresh.kumar@linaro.org, ping.bai@nxp.com, aisheng.dong@nxp.com
Subject: [PATCH 1/2] ARM: dts: imx6ul: add 696MHz operating point
Date: Wed, 3 Jan 2018 01:07:38 +0800	[thread overview]
Message-ID: <1514912859-17691-1-git-send-email-Anson.Huang@nxp.com> (raw)

Add 696MHz operating point according to datasheet
(Rev. 0, 12/2015).

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
 				528000	1175000
 				396000	1175000
 				198000	1175000
-- 
1.9.1

             reply	other threads:[~2018-01-02 17:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 17:07 Anson Huang [this message]
2018-01-02 15:03 ` [PATCH 1/2] ARM: dts: imx6ul: add 696MHz operating point Fabio Estevam
2018-01-02 15:12   ` Anson Huang
2018-01-02 15:32     ` Fabio Estevam
     [not found]       ` <CAOMZO5BGmnNzv7YobtB+KOi0PM+qzyYi97q_NZtT1PU_e+Bcbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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
2018-01-02 15:05     ` Anson Huang
     [not found]       ` <A2F3BA8B-361A-4809-83FE-4067CD868D5B-3arQi8VN3Tc@public.gmane.org>
2018-01-02 15:13         ` Fabio Estevam
2018-01-02 15:17           ` Anson Huang
     [not found]             ` <6FFDB281-8293-4D2C-891F-B376B52EFECF-3arQi8VN3Tc@public.gmane.org>
2018-01-02 15:33               ` Fabio Estevam
     [not found]                 ` <CAOMZO5ADWdbDoCO8b4JVDag=PH2MgLsLbQ6DJU8VvJh6G6qMkQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-03  2:10                   ` Anson Huang
     [not found]   ` <1514912859-17691-2-git-send-email-Anson.Huang-3arQi8VN3Tc@public.gmane.org>
2018-01-05 12:21     ` Rafael J. Wysocki
2018-01-06  3:05       ` Anson Huang
2018-01-07 23:34         ` Rafael J. Wysocki
     [not found]           ` <2009633.KF2URkV5n1-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
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=1514912859-17691-1-git-send-email-Anson.Huang@nxp.com \
    --to=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).