From f1642f0a2bbdb1abafb1469dd61c5e413f799336 Mon Sep 17 00:00:00 2001
From: kartanan <kartanan@quicinc.com>
Date: Wed, 28 Aug 2019 12:49:44 -0700
Subject: [PATCH] dt-bindings: camera: Add custom HW/csid bindings for KONA

The change adds device tree bindings for custom HW for KONA.

CRs-Fixed: 2515662
Change-Id: I3ee315c238275e5e4775c5a46a57636877ec44d7
---
 bindings/msm-cam-custom-hw.txt | 28 ++++++++++++++++++++++++++++
 bindings/msm-cam-custom.txt    | 31 +++++++++++++++++++++++++++++++
 bindings/msm-cam-ife-csid.txt  |  4 ++--
 3 files changed, 61 insertions(+), 2 deletions(-)
 create mode 100644 bindings/msm-cam-custom-hw.txt
 create mode 100644 bindings/msm-cam-custom.txt

diff --git a/bindings/msm-cam-custom-hw.txt b/bindings/msm-cam-custom-hw.txt
new file mode 100644
index 000000000000..61125d0c8087
--- /dev/null
+++ b/bindings/msm-cam-custom-hw.txt
@@ -0,0 +1,28 @@
+* Qualcomm Technologies, Inc. MSM Camera Custom HW
+
+Camera Custom device provides the definitions for enabling
+the custom hardware. It also provides the functions for the client
+to control the Custom hardware.
+
+=======================
+Required Node Structure
+=======================
+The Custom device is described in one level of the device node.
+
+======================================
+First Level Node - CAM Custom device
+======================================
+Required properties:
+- compatible
+  Usage: required
+  Value type: <string>
+  Definition: Should specify the compatibility string for matching the
+	driver. e.g. "qcom,cam_custom_hw_sub_mod".
+
+Example:
+
+	qcom,cam-custom-hw {
+		compatible = "qcom,cam_custom_hw_sub_mod";
+		arch-compat = "custom";
+		status = "ok";
+	};
diff --git a/bindings/msm-cam-custom.txt b/bindings/msm-cam-custom.txt
new file mode 100644
index 000000000000..8c5cc6148c5b
--- /dev/null
+++ b/bindings/msm-cam-custom.txt
@@ -0,0 +1,31 @@
+* Qualcomm Technologies, Inc. MSM Camera Custom
+
+The MSM camera Custom driver provides the definitions for enabling
+the Camera custom hadware. It provides the functions for the Client to
+control the custom hardware.
+
+=======================
+Required Node Structure
+=======================
+The camera Custom device is described in one level of device node.
+
+==================================
+First Level Node - CAM CUSTOM device
+==================================
+- compatible
+  Usage: required
+  Value type: <string>
+  Definition: Should be "qcom,cam-custom".
+
+- arch-compat
+  Usage: required
+  Value type: <string>
+  Definition: Should be "custom".
+
+Example:
+
+	qcom,cam-custom {
+		compatible = "qcom,cam-custom";
+		arch-compat = "custom";
+		status = "ok";
+	};
diff --git a/bindings/msm-cam-ife-csid.txt b/bindings/msm-cam-ife-csid.txt
index 9d1af9523e01..ecff78ee1b27 100644
--- a/bindings/msm-cam-ife-csid.txt
+++ b/bindings/msm-cam-ife-csid.txt
@@ -16,8 +16,8 @@ First Level Node - CAM IFE CSID device
   Usage: required
   Value type: <string>
   Definition: Should be "qcom,csid170", "qcom,csid175", "qcom,csid175_200",
-              "qcom,csid480", "qcom,csid-lite170", "qcom,csid-lite175"
-              or "qcom,csid-lite480".
+              "qcom,csid480", "qcom,csid-lite170", "qcom,csid-lite175",
+              "qcom,csid-lite480" or "qcom,csid-custom480".
 
 - cell-index
   Usage: required