On 02/12/2023 08:54, Tony Lindgren wrote: > The device uses a clock lane, and 1 to 4 DSI data lanes. Let's add the > data-lanes property starting at 1 similar to what the other bridge > bindings are doing. > > Let's also drop the data-lanes properties in the example for the DSI host > controller to avoid confusion. The configuration of the DSI host depends > on the controller used and is unrelated to the bridge binding. > > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> > --- > .../display/bridge/toshiba,tc358775.yaml | 21 ++++++++++++++++--- > 1 file changed, 18 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358775.yaml b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358775.yaml > --- a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358775.yaml > +++ b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358775.yaml > @@ -46,11 +46,26 @@ properties: > > properties: > port@0: > - $ref: /schemas/graph.yaml#/properties/port > + $ref: /schemas/graph.yaml#/$defs/port-base You need to add here additionalProperties: false Best regards, Krzysztof
