Hi Kevin. > > > > Any specific reason why this is not a ports node like used by many other > > display bindings? > > In other words - I think this is too simple. > We only support one display pipeline now, other interface, like > DP(DisplayPort), HDMI...will be add later... > > ports: > $ref: /schemas/types.yaml#/definitions/phandle-array > description: | > Should contain a list of phandles pointing to display interface port > of dpu devices.. dpu definitions as defined in > Documentation/devicetree/bindings/display/sprd/sprd,dpu.yaml There is nothing wrong having a ports node that is limited to a single port node. But please remember the binding describes the HW - so if the HW supports more than one port the binding should describe this. What the driver supports is not relevant for the binding. Sam _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
