From a27f59bff72326e5ff96d3aea9e011de612a457a Mon Sep 17 00:00:00 2001
From: Amir Vajid <avajid@quicinc.com>
Date: Sat, 5 Jan 2019 13:11:23 -0800
Subject: [PATCH 1/2] dt-bindings: Add DT bindings to support compute bound
 logic

This patch adds the DT bindings to specify compute bound logic
in 'compatible' field so that this functionality can be rolled
over in to memlat governor.

Change-Id: I43df33839880329c0ad37b8a8178a6cf60fc1148
---
 bindings/devfreq/arm-memlat-mon.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bindings/devfreq/arm-memlat-mon.txt b/bindings/devfreq/arm-memlat-mon.txt
index dff7e300e70b..8a96fe5a2aae 100644
--- a/bindings/devfreq/arm-memlat-mon.txt
+++ b/bindings/devfreq/arm-memlat-mon.txt
@@ -4,7 +4,7 @@ arm-memlat-mon is a device that represents the use of the PMU in ARM cores
 to measure the parameters for latency driven memory access patterns.
 
 Required properties:
-- compatible:			Must be "qcom,arm-memlat-mon"
+- compatible:			Must be "qcom,arm-memlat-mon" or "qcom,arm-cpu-mon"
 - qcom,cpulist:			List of CPU phandles to be monitored in a cluster
 - qcom,target-dev:		The DT device that corresponds to this master port
 - qcom,core-dev-table:		A mapping table of core frequency to a required bandwidth vote at the

From 00f319152e9413896ce3e0261631a2fcf2bffd5c Mon Sep 17 00:00:00 2001
From: Amir Vajid <avajid@quicinc.com>
Date: Wed, 16 Jan 2019 20:29:34 -0800
Subject: [PATCH 2/2] dt-bindings: devfreq: Add DT bindings to support OPP BW
 values

This patch adds DT bindings for the list of supported bandwidth
values added in device tree.

Change-Id: I0e8fd3ba3aeb6c98bc027a621455288606683fd3
---
 bindings/devfreq/devfreq_icc.txt | 47 ++++++++++++++++++++++----------
 1 file changed, 33 insertions(+), 14 deletions(-)

diff --git a/bindings/devfreq/devfreq_icc.txt b/bindings/devfreq/devfreq_icc.txt
index 1baac710ce73..5680740a66c3 100644
--- a/bindings/devfreq/devfreq_icc.txt
+++ b/bindings/devfreq/devfreq_icc.txt
@@ -10,11 +10,11 @@ Required properties:
 - interconnects:	Pairs of phandles and interconnect provider specificers
 			to denote the edge source and destination ports of the
 			desired interconnect path.
-- qcom,bw-tbl:		A list of meaningful instantaneous bandwidth values
-			(in MB/s) that can be requested from the device
-			master port to the slave port. The list of values
-			depend on the supported bus/slave frequencies and the
-			bus width.
+- operating-points-v2:	A phandle to the OPP v2 table that holds meaningful
+			instantaneous bandwidth values (in MB/s) that can be
+			requested from the device master port to the slave port.
+			The list of values depend on the supported bus/slave
+			frequencies and the bus width.
 
 Optional properties:
 - qcom,active-only:	Indicates that the bandwidth votes need to be
@@ -24,17 +24,36 @@ Optional properties:
 
 Example:
 
+	bw_opp_table: bw-opp-table {
+		compatible = "operating-points-v2";
+		opp-75  {
+			opp-hz = /bits/ 64 <  572 >; /*  75 MHz */
+		};
+		opp-150 {
+			opp-hz = /bits/ 64 < 1144 >; /* 150 MHz */
+		};
+		opp-200 {
+			opp-hz = /bits/ 64 < 1525 >; /* 200 MHz */
+		};
+		opp-307 {
+			opp-hz = /bits/ 64 < 2342 >; /* 307 MHz */
+		};
+		opp-460 {
+			opp-hz = /bits/ 64 < 3509 >; /* 460 MHz */
+		};
+		opp-614 {
+			opp-hz = /bits/ 64 < 4684 >; /* 614 MHz */
+		};
+		opp-800 {
+			opp-hz = /bits/ 64 < 6103 >; /* 800 MHz */
+		};
+		opp-931 {
+			opp-hz = /bits/ 64 < 7102 >; /* 931 MHz */
+		};
+	};
 	qcom,cpubw {
 		compatible = "qcom,devfreq-icc";
 		interconnects = <&mc_virt MASTER_LLCC &mc_virt SLAVE_EBI1>;
 		qcom,active-only;
-		qcom,bw-tbl =
-			<  572 /*  75 MHz */ >,
-			< 1144 /* 150 MHz */ >,
-			< 1525 /* 200 MHz */ >,
-			< 2342 /* 307 MHz */ >,
-			< 3509 /* 460 MHz */ >,
-			< 4684 /* 614 MHz */ >,
-			< 6103 /* 800 MHz */ >,
-			< 7102 /* 931 MHz */ >;
+		operating-points-v2 = <&bw_opp_table>;
 	};