devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-pm@vger.kernel.org
Cc: cpufreq@vger.kernel.org, devicetree@vger.kernel.org,
	kernel@pengutronix.de, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Jisheng Zhang <jszhang@marvell.com>,
	Anson Huang <Anson.Huang@freescale.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Nishanth Menon <nm@ti.com>, Dave Gerlach <d-gerlach@ti.com>
Subject: [RFC 8/9] ARM: dts: dra7: Add opp-modifier device entry and add higher OPPs
Date: Fri, 14 Mar 2014 14:25:34 -0500	[thread overview]
Message-ID: <1394825135-60110-9-git-send-email-d-gerlach@ti.com> (raw)
In-Reply-To: <1394825135-60110-1-git-send-email-d-gerlach@ti.com>

Add an entry for opp-modifier which configures OPPs on 43xx. Within
this, nodes are defined with the opp-modifier propety that are defined as
a list of frequency, offset from base register, and efuse value.
The CPU node passes a phandle to the appropriate child node to get the
correct table.

This patch also adds higher eFused OPPs for dra7.

Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
---
 arch/arm/boot/dts/dra7.dtsi  | 18 ++++++++++++++++++
 include/dt-bindings/opp/ti.h |  3 +++
 2 files changed, 21 insertions(+)

diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index 1fd75aa..ffd0bae 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++ b/arch/arm/boot/dts/dra7.dtsi
@@ -9,6 +9,7 @@
 
 #include <dt-bindings/interrupt-controller/arm-gic.h>
 #include <dt-bindings/pinctrl/dra.h>
+#include <dt-bindings/opp/ti.h>
 
 #include "skeleton.dtsi"
 
@@ -46,7 +47,10 @@
 				/* kHz    uV */
 				1000000	1060000
 				1176000	1160000
+				1500000	1260000
 				>;
+
+			platform-opp-modifier = <&mpu_opp_modifier>;
 		};
 		cpu@1 {
 			device_type = "cpu";
@@ -621,6 +625,20 @@
 			dma-names = "tx0", "rx0";
 			status = "disabled";
 		};
+
+		opp_modifier: opp_modifier@0x4AE0C20C {
+			compatible = "opp-modifier-reg-val";
+			reg = <0x4AE0C20C 0x04>;
+			opp,reg-mask = <0x000000F7>;
+
+			mpu_opp_modifier: mpu_opp_modifier {
+				opp-modifier = <
+				/* kHz	offset	value */
+				1500000	0	DRA7_EFUSE_HAS_HIGH_MPU_OPP
+				1176000	0	DRA7_EFUSE_HAS_OD_MPU_OPP
+				>;
+			};
+		};
 	};
 };
 
diff --git a/include/dt-bindings/opp/ti.h b/include/dt-bindings/opp/ti.h
index cb62c32..0f5efe8 100644
--- a/include/dt-bindings/opp/ti.h
+++ b/include/dt-bindings/opp/ti.h
@@ -27,4 +27,7 @@
 
 #define OMAP4_EFUSE_HAS_PERF_SILICON_BIT		(1 << 17)
 
+#define DRA7_EFUSE_HAS_OD_MPU_OPP			11
+#define DRA7_EFUSE_HAS_HIGH_MPU_OPP			15
+
 #endif		/* __DT_BINDINGS_OPP_TI_H__ */
-- 
1.9.0


  parent reply	other threads:[~2014-03-14 19:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 19:25 [RFC 0/9] Introduce OPP modifier for ARM SoCs Dave Gerlach
2014-03-14 19:25 ` [RFC 1/9] opp-modifier: Introduce OPP Modifier Framework Dave Gerlach
2014-03-14 19:25 ` [RFC 2/9] opp-modifier: Add opp-modifier-reg driver Dave Gerlach
2014-03-14 21:00   ` Rob Herring
2014-03-17 14:30     ` Nishanth Menon
2014-03-17 18:37       ` Rob Herring
2014-03-18 15:36         ` Nishanth Menon
2014-03-25  3:24           ` Dave Gerlach
2014-03-14 19:25 ` [RFC 3/9] PM / OPP: Add hook to modify OPPs after they are loaded Dave Gerlach
2014-03-14 19:25 ` [RFC 4/9] ARM: dts: AM33XX: Add opp-modifier device entry and add higher OPPs Dave Gerlach
2014-03-14 19:25 ` [RFC 5/9] ARM: dts: AM4372: " Dave Gerlach
2014-03-14 19:25 ` [RFC 6/9] ARM: dts: omap443x: Add opp-modifier " Dave Gerlach
2014-03-14 19:25 ` [RFC 7/9] ARM: dts: omap4460: " Dave Gerlach
2014-03-14 19:25 ` Dave Gerlach [this message]
2014-03-14 19:25 ` [RFC 9/9] ARM: dts: imx6q: Add opp-modifier device entry Dave Gerlach

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=1394825135-60110-9-git-send-email-d-gerlach@ti.com \
    --to=d-gerlach@ti.com \
    --cc=Anson.Huang@freescale.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jszhang@marvell.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=shawn.guo@linaro.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).