DCP platforms place the display pipeline under firmware control, so Linux cannot discover display resources through direct register access. The DRM driver therefore needs device-tree descriptions of the firmware transport, display topology, IOMMU contexts, and panel connections.
Add bindings for the Qualcomm DCP VirtIO display function, including the INTF graph and DSI host outputs. Document the framebuffer IOMMU context, IPCC power-notify mailbox and interrupts, firmware display topology, and firmware-visible IOVA window supplied by the parent VirtIO-MMIO transport. Signed-off-by: Jayant Shekhar <[email protected]> Assisted-by: LLM --- .../bindings/display/msm/qcom,dcp-dsi.yaml | 75 +++++++++++++ .../bindings/display/msm/qcom,dcp-virtio.yaml | 113 +++++++++++++++++++ .../devicetree/bindings/display/msm/qcom,dcp.yaml | 119 +++++++++++++++++++++ 3 files changed, 307 insertions(+) diff --git a/Documentation/devicetree/bindings/display/msm/qcom,dcp-dsi.yaml b/Documentation/devicetree/bindings/display/msm/qcom,dcp-dsi.yaml new file mode 100644 index 000000000000..f7178c66c09e --- /dev/null +++ b/Documentation/devicetree/bindings/display/msm/qcom,dcp-dsi.yaml @@ -0,0 +1,75 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/msm/qcom,dcp-dsi.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Qualcomm DCP DSI host + +maintainers: + - Jayant Shekhar <[email protected]> + +description: | + A MIPI DSI host exposed by the Qualcomm DCP VirtIO device (see + qcom,dcp.yaml). DCP is a firmware protocol shared across multiple + Qualcomm SoCs, not specific to any one of them; Hawi is its first + platform. The DSI host and its connection to a panel are described + using the standard DSI controller and OF graph properties. + +allOf: + - $ref: /schemas/display/dsi-controller.yaml# + +properties: + reg: + maxItems: 1 + description: Index of this DSI host among its siblings. + + status: true + + ports: + $ref: /schemas/graph.yaml#/properties/ports + description: | + port@0: Input from the DCP virtio device's DPU INTF output port. + port@1: Output to the attached panel. + properties: + port@0: + $ref: /schemas/graph.yaml#/properties/port + port@1: + $ref: /schemas/graph.yaml#/$defs/port-base + unevaluatedProperties: false + properties: + endpoint: + $ref: /schemas/media/video-interfaces.yaml# + unevaluatedProperties: false + +required: + - reg + - ports + +unevaluatedProperties: false + +examples: + - | + dcp-subsystem { + #address-cells = <1>; + #size-cells = <0>; + + dsi@0 { + reg = <0>; + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + dcp_dsi0_in: endpoint { + remote-endpoint = <&dcp_intf1_out>; + }; + }; + + }; + }; + }; diff --git a/Documentation/devicetree/bindings/display/msm/qcom,dcp-virtio.yaml b/Documentation/devicetree/bindings/display/msm/qcom,dcp-virtio.yaml new file mode 100644 index 000000000000..018694310dfb --- /dev/null +++ b/Documentation/devicetree/bindings/display/msm/qcom,dcp-virtio.yaml @@ -0,0 +1,113 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/msm/qcom,dcp-virtio.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Qualcomm DCP VirtIO host + +maintainers: + - Jayant Shekhar <[email protected]> + +description: | + Qualcomm's DCP VirtIO host provides the generic VirtIO-MMIO transport and + the host-side IPCC channel used to wake the DCP firmware. + +properties: + compatible: + contains: + const: qcom,dcp-virtio + + reg: + maxItems: 1 + + iommus: + maxItems: 1 + + iommu-ranges: + $ref: /schemas/types.yaml#/definitions/uint32-array + + interrupts-extended: + minItems: 2 + + interrupt-names: + items: + - const: virtio + - const: dcp_power_notify_irq + + dma-coherent: true + + mboxes: + maxItems: 1 + + mbox-names: + const: dcp-power-tx + + dcp-subsystem: + $ref: qcom,dcp.yaml# + +required: + - compatible + - reg + - interrupts-extended + - interrupt-names + - iommus + - dcp-subsystem + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/arm-gic.h> + #include <dt-bindings/mailbox/qcom-ipcc.h> + + virtio@9be8000 { + compatible = "qcom,dcp-virtio", "virtio,mmio"; + reg = <0x09be8000 0x1000>; + interrupts-extended = <&intc GIC_ESPI 956 IRQ_TYPE_LEVEL_HIGH>, + <&ipcc 13 5 IRQ_TYPE_EDGE_RISING>; + interrupt-names = "virtio", "dcp_power_notify_irq"; + iommus = <&apps_smmu 0x15a3 0x0>; + iommu-ranges = <0x0 0x84000000 0x0 0x04000000>; + dma-coherent; + mboxes = <&ipcc 13 5>; + mbox-names = "dcp-power-tx"; + + dcp-subsystem { + compatible = "virtio,device34"; + iommus = <&apps_smmu 0x400 0x2>; + + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@1 { + reg = <1>; + dcp_intf1_out: endpoint { + remote-endpoint = <&dcp_dsi0_in>; + }; + }; + }; + + dsi@0 { + reg = <0>; + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + dcp_dsi0_in: endpoint { + remote-endpoint = <&dcp_intf1_out>; + }; + }; + }; + }; + }; + }; diff --git a/Documentation/devicetree/bindings/display/msm/qcom,dcp.yaml b/Documentation/devicetree/bindings/display/msm/qcom,dcp.yaml new file mode 100644 index 000000000000..0ca00a567e9e --- /dev/null +++ b/Documentation/devicetree/bindings/display/msm/qcom,dcp.yaml @@ -0,0 +1,119 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/msm/qcom,dcp.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Qualcomm Display Co-Processor (DCP) + +maintainers: + - Jayant Shekhar <[email protected]> + +description: | + The Display Co-Processor (DCP) is a firmware-owned display subsystem. + Linux communicates with DCP over HFI through VirtIO and does not access + display hardware registers directly. + + This node describes the externally connected display graph between DCP + INTF outputs and DSI hosts. Firmware capabilities and internal resources, + including pipes, mixers, CRTCs, and clocks, are discovered at runtime. + + The compatible string "virtio,device34" encodes device ID 52 (0x34). It is + a provisional local ID pending registration of the DCP HFI VirtIO device. + +allOf: + - $ref: /schemas/virtio/virtio-device.yaml# + +properties: + compatible: + const: virtio,device34 + + iommus: + maxItems: 1 + description: + SMMU context used by DCP firmware to access GEM framebuffers. This + is separate from the HFI transport context specified by the + iommus property on the parent virtio,mmio node. + The child context is used for framebuffer DMA performed by DCP + firmware, while the parent context is used for VirtIO transport and HFI + queue buffers. These contexts represent distinct firmware-visible DMA + address spaces and must not be used interchangeably. + + "#address-cells": + const: 1 + + "#size-cells": + const: 0 + + ports: + $ref: /schemas/graph.yaml#/properties/ports + description: | + DPU INTF output ports. Port number matches INTF index: + port@0: INTF0 (no bridge in this series) + port@1: INTF1 -> DSI0 + port@2: INTF2 -> DSI1 + port@3: INTF3 (no bridge in this series) + properties: + port@0: + $ref: /schemas/graph.yaml#/properties/port + port@1: + $ref: /schemas/graph.yaml#/properties/port + port@2: + $ref: /schemas/graph.yaml#/properties/port + port@3: + $ref: /schemas/graph.yaml#/properties/port + +patternProperties: + "^dsi@[0-9]+$": + $ref: qcom,dcp-dsi.yaml# + +required: + - compatible + - iommus + - "#address-cells" + - "#size-cells" + - ports + +unevaluatedProperties: false + +examples: + - | + dcp-subsystem { + compatible = "virtio,device34"; + + iommus = <&apps_smmu 0x400 0x2>; + + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@1 { + reg = <1>; + dcp_intf1_out: endpoint { + remote-endpoint = <&dcp_dsi0_in>; + }; + }; + }; + + dsi@0 { + reg = <0>; + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + dcp_dsi0_in: endpoint { + remote-endpoint = <&dcp_intf1_out>; + }; + }; + + }; + }; + }; -- 2.43.0
