On Thu, Oct 15, 2026 at 01:08:21PM +0530, Jayant Shekhar wrote: > 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.
Due to dependencies this cannot be tested, so limited review. A nit, subject: drop second/last, redundant "bindings". The "dt-bindings" prefix is already stating that these are bindings. See also: https://elixir.bootlin.com/linux/v7.1-rc7/source/Documentation/devicetree/bindings/submitting-patches.rst#L23 > > 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 I see slop, I finished here. Mind this maintainers summit words - if you use AI, you must use good one, not the shloppy slop. Best regards, Krzysztof
