From 85ddb3e7b18ba320cab82a35dbbf4aa20ef420f8 Mon Sep 17 00:00:00 2001
From: Naveen Yadav <naveenky@qti.qualcomm.com>
Date: Tue, 2 Jun 2020 14:41:12 +0530
Subject: [PATCH 1/2] dt-bindings: interconnect: add interconnect bindings for
 SDXLEMUR

Add interconnect device bindings. These devices can be used to
describe any RPMH and NoC based interconnect devices.

Change-Id: Ice8cf23e6fc6251addd2976ee8acd95eb2c88c2d
---
 bindings/interconnect/qcom,sdxlemur.txt | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 bindings/interconnect/qcom,sdxlemur.txt

diff --git a/bindings/interconnect/qcom,sdxlemur.txt b/bindings/interconnect/qcom,sdxlemur.txt
new file mode 100644
index 000000000000..03642c286c71
--- /dev/null
+++ b/bindings/interconnect/qcom,sdxlemur.txt
@@ -0,0 +1,23 @@
+Qualcomm Technologies, Inc. SDXLEMUR Network-On-Chip interconnect driver binding
+--------------------------------------------------------------------------------
+
+SDXLEMUR interconnect providers support system bandwidth requirements through
+RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
+able to communicate with the BCM through the Resource State Coordinator (RSC)
+associated with each execution environment. Provider nodes must point to at
+least one RPMh device child node pertaining to their RSC and each provider
+can map to multiple RPMh resources.
+
+Required properties :
+- compatible : shall contain only one of the following:
+			"qcom,sdxlemur-system_noc",
+			"qcom,sdxlemur-mem_noc",
+			"qcom,sdxlemur-mc_virt",
+- #interconnect-cells : should contain 1
+
+Examples:
+
+system_noc: interconnect@1620000 {
+	compatible = "qcom,sdxlemur-system_noc";
+	interconnect-cells = <1>;
+};

From 820c448e1fcb48893cff056c3147e198e6d11075 Mon Sep 17 00:00:00 2001
From: Naveen Yadav <naveenky@qti.qualcomm.com>
Date: Thu, 28 May 2020 12:51:49 +0530
Subject: [PATCH 2/2] ARM: dts: msm: Add stub interconnect devices for sdxlemur

Add stub interconnect devices for system_noc, mem_noc, mc_virt
and ipa_virt. This will allow consumers to get their path and
set bandwidth constraints on them.

Change-Id: I37af153914bf86da471f220976522cc336dcdd37
---
 qcom/sdxlemur.dtsi | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/qcom/sdxlemur.dtsi b/qcom/sdxlemur.dtsi
index 995257f5bb62..128fac1dfc7d 100644
--- a/qcom/sdxlemur.dtsi
+++ b/qcom/sdxlemur.dtsi
@@ -3,6 +3,7 @@
 #include <dt-bindings/clock/qcom,gcc-sdxlemur.h>
 #include <dt-bindings/clock/qcom,rpmh.h>
 #include <dt-bindings/interrupt-controller/arm-gic.h>
+#include <dt-bindings/interconnect/qcom,sdxlemur.h>
 
 / {
 	#address-cells = <1>;
@@ -266,6 +267,21 @@
 		reg = <0x117004 0x4>;
 		regulator-name = "gcc_usb30_gdsc";
 	};
+
+	system_noc: interconnect@1620000 {
+		compatible = "qcom,sdxlemur-system_noc";
+		#interconnect-cells = <1>;
+	};
+
+	mem_noc: interconnect@9680000 {
+		compatible = "qcom,sdxlemur-mem_noc";
+		#interconnect-cells = <1>;
+	};
+
+	mc_virt: interconnect {
+		compatible = "qcom,sdxlemur-mc_virt";
+		#interconnect-cells = <1>;
+	};
 };
 
 #include "sdxlemur-pinctrl.dtsi"