Re: [PATCH v2 01/23] dt-bindings: display: msm: Add Qualcomm DCP

[Jayant Shekhar <jayant.shekhar@oss.qualcomm.com>]

On 27-10-2026 14:06, Krzysztof Kozlowski wrote:
> On Mon, Oct 26, 2026 at 11:51:11AM +0530, Jayant Shekhar wrote:
>> DCP platforms place the display pipeline under firmware control, so Linux
> What is a DCP platform?
>

Will address this in v3.


>> cannot discover display resources through direct register access. The DRM
>> driver therefore needs device-tree descriptions of the Qualcomm transport
>> wrapper, display topology, IOMMU contexts, and panel connections.
>>
>> Add bindings for the Qualcomm DCP transport wrapper and VirtIO display
>> subsystem. Document the IPCC power-notify resources, transport and
>> framebuffer IOMMU contexts, firmware-visible IOVA range, INTF graph, and
>> DSI panel connections. The wrapper creates a standard VirtIO-MMIO child
>> after the IPCC power-notify sequence has completed.
> It's still DT for real hardware, so I wonder why no SoC specific
> compatibles were used.


Thanks. The same DCP transport wrapper works on Hawi and Maili, so the 
current driver uses the generic qcom,dcp-virtio compatible.

If a future SoC requires different wrapper handling or has a different 
layout, we can add a SoC-

specific compatible and match data then. The child’s virtio,device34 
compatible identifies the VirtIO function.


> Best regards,
> Krzysztof