[PATCH 1/3] dt-bindings: display: bridge: document TH1520 MIPI DSI controller

[Icenowy Zheng]

在 2026-11-02一的 12:28 +0100，Krzysztof Kozlowski写道：
> On Fri, Oct 30, 2026 at 03:47:49PM +0800, Icenowy Zheng wrote:
> > +  interrupts:
> > +    maxItems: 1
> > +
> > +  clocks:
> > +    items:
> > +      - description: DSI controller APB clock
> > +      - description: PHY configuration clock
> > +      - description: PHY reference clock
> > +      - description: DSI controller input pixel clock gate
> > +
> > +  clock-names:
> > +    items:
> > +      - const: pclk
> > +      - const: phy_cfg
> > +      - const: ref
> > +      - const: pixel
> > +
> > +  syscon:
> 
> Such property names are not allowed. Missing vendor prefix, missing
> descriptive name.

Sorry because I thought `syscon` is a generic name -- it's available as
a compatible string (although with SoC-specific fallbacks) in
mfd/syscon.yaml . I'm okay to name this property `thead,syscon` or
`thead,vosys-syscon` .

> 
> > +    $ref: /schemas/types.yaml#/definitions/phandle
> > +    description:
> > +      Phandle to the VO subsystem system controller.
> 
> For what purpose? How does this device use VO? What is VO subsystem
> system?

VO is short for "Video Output", the name for one of the "subsystems" on
TH1520, and this abbreviation is used in the user manual in strings as
"VO_SUBSYS". A certain register is wired to D-PHY sideband signals and
thus bound to the DSI controller.

Should I add the information in the last sentence to the binding?

Thanks,
Icenowy

> 
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - clocks
> > +  - clock-names
> > +  - resets
> > +  - reset-names
> > +  - interrupts
> > +  - syscon
> > +  - ports
> 
> Best regards,
> Krzysztof