On Fri, Oct 29, 2021 at 10:28:22AM +0200, Geert Uytterhoeven wrote:
Hi Russell,
Thanks for your comments!
No, you can still use port:
+oneOf:
- required:
- port
- required:
- portsWhen using ports, no further requirements are set, but perhaps port@0 should be made required in that case?
Maybe I don't understand the binding description then, but to me it looks like you require both port@0 and port@1.
The reality of the driver is that it makes almost no use of the graph itself, except via drm_of_find_possible_crtcs() to find the connected CRTCs. If it is connected to an I2S source, then it probably needs a port specification for that. If someone wants to describe the HDMI connector (which I don't see any point in) then they likely need a port specification for that too. However, the driver itself doesn't care about any of those.
So, describing the port nodes makes no sense.