From da253f6d42ccc38ffb34d2c852afe66b2853d2b0 Mon Sep 17 00:00:00 2001
From: Gokul krishna Krishnakumar <gokukris@quicinc.com>
Date: Sun, 15 Aug 2021 19:16:11 -0700
Subject: [PATCH] dt-bindings: Add device-tree bindings for memory dump v2

Add device-tree bindings documentation for memory dump v2 properties.

Change-Id: I620922d2e128bbb8635773d949f88940772d1a29
---
 bindings/arm/msm/msm_memory_dump.txt | 32 ++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 bindings/arm/msm/msm_memory_dump.txt

diff --git a/bindings/arm/msm/msm_memory_dump.txt b/bindings/arm/msm/msm_memory_dump.txt
new file mode 100644
index 00000000..c2bb7b3e
--- /dev/null
+++ b/bindings/arm/msm/msm_memory_dump.txt
@@ -0,0 +1,32 @@
+Qualcomm Technologies Inc. memory dump driver
+
+QTI memory dump driver allows various client subsystems to register and
+allocate respective dump regions. At the time of deadlocks or cpu hangs
+these dump regions are captured to give a snapshot of the system at the
+time of the crash.
+
+Required properties:
+
+-compatible: "qcom,mem-dump"
+-memory-region: phandle to the CMA region. The size of the CMA region
+		should be greater than sum of size of all child nodes
+		to account for padding.
+
+If any child nodes exist the following property are required:
+
+-qcom,dump-size: The size of memory that needs to be allocated for the
+		 particular node.
+-qcom,dump-id: The ID within the data dump table where this entry needs
+	       to be added.
+
+Example:
+
+	mem_dump {
+		compatible = "qcom,mem-dump";
+		memory-region = <&dump_mem>;
+
+		rpmh_dump {
+			qcom,dump-size = <0x2000000>;
+			qcom,dump-id = <0xEC>;
+		};
+	};