Merge "dt-bindings: net: Add bindings for the qrtr-mhi driver"

bindings/net/qcom-qrtr-mhi.yaml

@@ -0,0 +1,62 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/net/qcom-qrtr-mhi.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: QTI QRTR MHI transport Configuration
+
+maintainers:
+  - Lei Han <quic_leihan@quicinc.com>
+
+description: |
+  Configuration properties for the qrtr MHI Transport.
+  This configuration is to instantiate a transport for
+  IPC Router protocol communication between APPS and
+  external modems.
+
+properties:
+  compatible:
+    enum:
+      - qcom,qrtr-mhi
+      - qcom,qrtr-mhi-dev
+
+  qcom,dev-id:
+    $ref: '/schemas/types.yaml#/definitions/uint32'
+    maxItems: 1
+    description:
+      indicates the dev-id that this transport is for.
+      Should be passed into the qrtr core logic to determine
+      to match with the dev-id used by the mhi controller.
+
+  qcom,net-id:
+    $ref: '/schemas/types.yaml#/definitions/uint32'
+    maxItems: 1
+    description:
+      indicates what subnet this transport belongs to.
+      If the dev-id passed above matches the one passed into qrtr
+      logic by mhi core, then this net-id is passed into the qrtr
+      core logic to determin if forwarding is needed on this endpoint.
+
+  qcom,low-latency:
+    type: boolean
+    description:
+      indicates whether this transport receiving thread needs
+      to be set to realtime priority for enhanced performance.
+
+required:
+  - compatible
+
+additionalProperties: false
+
+examples:
+  #The following example represents the qrtr mhi transport node on
+  #a device configured as a pcie endpoint and needs to forward data
+  #from the host to a slpi co-processor.
+  - |
+    mhi_qrtr_cnss {
+        compatible = "qcom,qrtr-mhi";
+        qcom,dev-id = <0x1103>;
+        qcom,net-id = <0>;
+        qcom,low-latency;
+    };