summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinux Build Service Account <lnxbuild@localhost>2019-09-10 06:46:37 -0700
committerLinux Build Service Account <lnxbuild@localhost>2019-09-10 06:46:37 -0700
commit50765a66c58b918a10cd528b702dc1235300777d (patch)
tree1d060af219565a882caa1bba422cb2de79a25cc3
parenta9b6d791f5d260f2d1346924905d737d07b18368 (diff)
parentf1642f0a2bbdb1abafb1469dd61c5e413f799336 (diff)
downloadcamera-devicetree-50765a66c58b918a10cd528b702dc1235300777d.tar.gz
Merge f1642f0a2bbdb1abafb1469dd61c5e413f799336 on remote branch
Change-Id: Id573880015288eb277c06dba6cc8586c82b9999c
-rw-r--r--bindings/msm-cam-custom-hw.txt28
-rw-r--r--bindings/msm-cam-custom.txt31
-rw-r--r--bindings/msm-cam-ife-csid.txt4
3 files changed, 61 insertions, 2 deletions
diff --git a/bindings/msm-cam-custom-hw.txt b/bindings/msm-cam-custom-hw.txt
new file mode 100644
index 0000000..61125d0
--- /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 0000000..8c5cc61
--- /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 9d1af95..ecff78e 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