Hi Marek On Wed, 12 Aug 2020 at 21:07, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > > Hi Marek. > > On Sun, Aug 09, 2020 at 12:57:04PM +0200, Marek Vasut wrote: > > Add DT bindings for Toshiba TC358762 DSI-to-DPI bridge, this > > one is used in the Raspberry Pi 7" touchscreen display unit. > > > > Signed-off-by: Marek Vasut <marex@xxxxxxx> > > To: dri-devel@xxxxxxxxxxxxxxxxxxxxx > > Cc: Eric Anholt <eric@xxxxxxxxxx> > > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > > Cc: Sam Ravnborg <sam@xxxxxxxxxxxx> > > Cc: devicetree@xxxxxxxxxxxxxxx > > --- > > V2: Fix dt_binding_check errors > > V3: Add ... at the end of example > > With Rob's r-b it is now applied to drm-misc-next. > > Sam > > > --- > > .../display/bridge/toshiba,tc358762.yaml | 127 ++++++++++++++++++ > > 1 file changed, 127 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358762.yaml > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/toshiba,tc358762.yaml b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358762.yaml > > new file mode 100644 > > index 000000000000..195025e6803c > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/display/bridge/toshiba,tc358762.yaml > > @@ -0,0 +1,127 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/display/bridge/toshiba,tc358762.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Toshiba TC358762 MIPI DSI to MIPI DPI bridge > > + > > +maintainers: > > + - Marek Vasut <marex@xxxxxxx> > > + > > +description: | > > + The TC358762 is bridge device which converts MIPI DSI to MIPI DPI. > > + > > +properties: > > + compatible: > > + enum: > > + - toshiba,tc358762 > > + > > + reg: > > + maxItems: 1 > > + description: virtual channel number of a DSI peripheral > > + > > + vddc-supply: > > + description: Regulator for 1.2V internal core power. > > + > > + ports: > > + type: object > > + > > + properties: > > + "#address-cells": > > + const: 1 > > + > > + "#size-cells": > > + const: 0 > > + > > + port@0: > > + type: object > > + additionalProperties: false > > + > > + description: | > > + Video port for MIPI DSI input > > + > > + properties: > > + reg: > > + const: 0 > > + > > + patternProperties: > > + endpoint: > > + type: object > > + additionalProperties: false > > + > > + properties: > > + remote-endpoint: true > > + > > + required: > > + - reg > > + > > + port@1: > > + type: object > > + additionalProperties: false > > + > > + description: | > > + Video port for MIPI DPI output (panel or connector). > > + > > + properties: > > + reg: > > + const: 1 > > + > > + patternProperties: > > + endpoint: > > + type: object > > + additionalProperties: false > > + > > + properties: > > + remote-endpoint: true > > + > > + required: > > + - reg > > + > > + required: > > + - "#address-cells" > > + - "#size-cells" > > + - port@0 > > + - port@1 > > + > > +required: > > + - compatible > > + - reg > > + - vddc-supply > > + - ports > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + i2c1 { Minor point. I've just come to use this and noticed that this example puts the device under i2c1. Seeing as it's a DSI driver with no I2C interaction, shouldn't it be under a dsi node? Thanks Dave > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + bridge@0 { > > + reg = <0>; > > + compatible = "toshiba,tc358762"; > > + vddc-supply = <&vcc_1v2_reg>; > > + > > + ports { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + port@0 { > > + reg = <0>; > > + bridge_in: endpoint { > > + remote-endpoint = <&dsi_out>; > > + }; > > + }; > > + > > + port@1 { > > + reg = <1>; > > + bridge_out: endpoint { > > + remote-endpoint = <&panel_in>; > > + }; > > + }; > > + }; > > + }; > > + }; > > + > > +... > > -- > > 2.28.0 > _______________________________________________ > dri-devel mailing list > dri-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/dri-devel _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel