On 19/07/2025 14:09, Otto Pflüger wrote: > diff --git > a/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dpu.yaml > b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dpu.yaml > index > 4ebea60b8c5ba5f177854e3a8d89e93e7304e18b..6fedb6e508b247eb71da17ced589b8ed09085592 > 100644 > --- a/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dpu.yaml > +++ b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dpu.yaml > @@ -16,7 +16,12 @@ description: | > > properties: > compatible: > - const: sprd,sharkl3-dpu > + oneOf: > + - items: > + - enum: > + - sprd,ums9230-dpu > + - const: sprd,sharkl3-dpu > + - const: sprd,sharkl3-dpu > > reg: > maxItems: 1 > @@ -25,12 +30,15 @@ properties: > maxItems: 1 > > clocks: > - minItems: 2 > + minItems: 1
This is wrong. You miss maxItems. I will fix existing bindings. > > clock-names: > - items: > - - const: clk_src_128m > - - const: clk_src_384m > + oneOf: > + - items: > + - const: clk_src_128m > + - const: clk_src_384m > + - items: > + - const: enable > > power-domains: > maxItems: 1 > diff --git > a/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml > b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml > index > bc5594d18643010b91376c92a8f235a522d7dc3d..8438d2da0a4277db03e30b13cb270684c0c360cb > 100644 > --- > a/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml > +++ > b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml > @@ -11,7 +11,9 @@ maintainers: > > properties: > compatible: > - const: sprd,sharkl3-dsi-host > + enum: > + - sprd,sharkl3-dsi-host > + - sprd,ums9230-dsi-host > > reg: > maxItems: 1 > @@ -23,8 +25,11 @@ properties: > minItems: 1 > > clock-names: > - items: > - - const: clk_src_96m > + oneOf: > + - items: > + - const: clk_src_96m > + - items: > + - const: enable Why this is completely different clock? How same class device could have completely different clock INPUT? > > power-domains: > maxItems: 1 > Best regards, Krzysztof
