Hi Marek, Thank you for the patch.
On Sat, Nov 27, 2021 at 04:24:02AM +0100, Marek Vasut wrote: > The TC358767/TC358867/TC9595 are all capable of operating in multiple > modes, DPI-to-(e)DP, DSI-to-(e)DP, DSI-to-DPI. Document support for the > DPI output port, which can now be connected both as input and output. > > Signed-off-by: Marek Vasut <ma...@denx.de> > Cc: Andrzej Hajda <a.ha...@samsung.com> > Cc: Jernej Skrabec <jernej.skra...@siol.net> > Cc: Jonas Karlman <jo...@kwiboo.se> > Cc: Laurent Pinchart <laurent.pinch...@ideasonboard.com> > Cc: Neil Armstrong <narmstr...@baylibre.com> > Cc: Rob Herring <robh...@kernel.org> > Cc: Sam Ravnborg <s...@ravnborg.org> > Cc: devicet...@vger.kernel.org > To: dri-devel@lists.freedesktop.org > --- > .../devicetree/bindings/display/bridge/toshiba,tc358767.yaml | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git > a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml > b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml > index f1541cc05297..5cfda6f2ba69 100644 > --- a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml > +++ b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml > @@ -61,8 +61,8 @@ properties: > port@1: > $ref: /schemas/graph.yaml#/properties/port > description: | > - DPI input port. The remote endpoint phandle should be a > - reference to a valid DPI output endpoint node > + DPI input/output port. The remote endpoint phandle should be a > + reference to a valid DPI output or input endpoint node. I assume the mode of operation (input or output) will be fixed for a given hardware design. Isn't this something that should be recorded in DT ? It would simplify configuration of the device in the driver. > > port@2: > $ref: /schemas/graph.yaml#/properties/port > -- Regards, Laurent Pinchart
