From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: srk@48.io Cc: Andrzej Hajda <a.hajda@samsung.com>, Neil Armstrong <narmstrong@baylibre.com>, Jonas Karlman <jonas@kwiboo.se>, Jernej Skrabec <jernej.skrabec@siol.net>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>, Lubomir Rintel <lkundrak@v3.sk>, dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Marek Vasut <marex@denx.de>, Sean Cross <xobs@kosagi.com> Subject: Re: [PATCH 1/2] dt-bindings: it6251: add bindings for IT6251 LVDS-to-eDP bridge Date: Sat, 9 May 2020 16:44:10 +0300 [thread overview] Message-ID: <20200509134410.GA5946@pendragon.ideasonboard.com> (raw) In-Reply-To: <20200509111732.26102-2-srk@48.io> Hi Richard, Thank you for the patch. On Sat, May 09, 2020 at 01:17:31PM +0200, srk@48.io wrote: > From: Marek Vasut <marex@denx.de> > > Add DT bindings for ITE IT6251 LVDS-to-eDP bridge. > > Signed-off-by: Marek Vasut <marex@denx.de> > Signed-off-by: Richard Marko <srk@48.io> > Cc: Daniel Vetter <daniel@ffwll.ch> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Sean Cross <xobs@kosagi.com> > Cc: devicetree@vger.kernel.org > To: dri-devel@lists.freedesktop.org > --- > .../bindings/display/bridge/ite,it6251.yaml | 97 +++++++++++++++++++ > 1 file changed, 97 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml > > diff --git a/Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml b/Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml > new file mode 100644 > index 000000000000..8daa44a30fa1 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml > @@ -0,0 +1,97 @@ > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/bridge/ite,it6251.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: ITE IT6251 LVDS-to-eDP bridge bindings > + > +maintainers: > + - Marek Vasut <marex@denx.de> > + - Richard Marko <srk@48.io> > + > +description: | > + The IT6251 is a high-performance single-chip > + De-SSC LVDS to DisplayPort converter. > + Combined with LVDS receiver and DisplayPort Transmitter, > + the IT6251 supports LVDS input and DisplayPort 1.1a > + output by conversion function. You could reflow this to the 80 columns limit. It also sounds like marketing material copied from the datasheet, with "by conversion function" likely a bad translation. > + > +properties: > + compatible: > + const: ite,it6251 > + > + reg: > + items: > + - description: I2C address of the bridge > + - description: I2C address of the LVDS part > + > + reg-names: > + items: > + - const: bridge > + - const: lvds > + > + ports: > + type: object > + > + properties: > + "#address-cells": > + const: 1 > + > + "#size-cells": > + const: 0 > + > + port@0: > + type: object > + description: | > + Video port for eDP output (typically panel). > + > + port@1: > + type: object > + description: | > + Video port for LVDS input. We traditionally use port 0 for the input and port 1 for the output. I'd rather do the same here to remain consistent, and allow generic code to operate on this device. > + > + required: > + - port@0 > + - port@1 > + > + additionalProperties: false > + > + power-supply: true There are multiple power supplies for the chip, shouldn't we have multiple properties ? I would also name the properties according to the supply name. The chip has an HPD input. I would recommend already documenting an optional boolean no-hpd property to report when the HPD input is not connected. > + > +required: > + - compatible > + - reg > + - reg-names > + - power-supply > + - ports > + > +additionalProperties: false > + > +examples: > + - | > + it6251@5c { > + compatible = "ite,it6251"; > + reg = <0x5c>, <0x5e>; > + reg-names = "bridge", "lvds"; > + power-supply = <®_display>; > + > + ports { > + #address-cells = <1>; > + #size-cells = <0>; > + > + port@0 { > + reg = <0>; > + bridge_out_edp0: endpoint { > + remote-endpoint = <&panel_in_edp0>; > + }; > + }; > + > + port@1 { > + reg = <1>; > + bridge_in_lvds0: endpoint { > + remote-endpoint = <&lvds0_out>; > + }; > + }; > + }; > + }; -- Regards, Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: srk@48.io Cc: Marek Vasut <marex@denx.de>, devicetree@vger.kernel.org, Jernej Skrabec <jernej.skrabec@siol.net>, Jonas Karlman <jonas@kwiboo.se>, David Airlie <airlied@linux.ie>, Neil Armstrong <narmstrong@baylibre.com>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Andrzej Hajda <a.hajda@samsung.com>, Lubomir Rintel <lkundrak@v3.sk>, Rob Herring <robh+dt@kernel.org>, Sean Cross <xobs@kosagi.com> Subject: Re: [PATCH 1/2] dt-bindings: it6251: add bindings for IT6251 LVDS-to-eDP bridge Date: Sat, 9 May 2020 16:44:10 +0300 [thread overview] Message-ID: <20200509134410.GA5946@pendragon.ideasonboard.com> (raw) In-Reply-To: <20200509111732.26102-2-srk@48.io> Hi Richard, Thank you for the patch. On Sat, May 09, 2020 at 01:17:31PM +0200, srk@48.io wrote: > From: Marek Vasut <marex@denx.de> > > Add DT bindings for ITE IT6251 LVDS-to-eDP bridge. > > Signed-off-by: Marek Vasut <marex@denx.de> > Signed-off-by: Richard Marko <srk@48.io> > Cc: Daniel Vetter <daniel@ffwll.ch> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Sean Cross <xobs@kosagi.com> > Cc: devicetree@vger.kernel.org > To: dri-devel@lists.freedesktop.org > --- > .../bindings/display/bridge/ite,it6251.yaml | 97 +++++++++++++++++++ > 1 file changed, 97 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml > > diff --git a/Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml b/Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml > new file mode 100644 > index 000000000000..8daa44a30fa1 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/ite,it6251.yaml > @@ -0,0 +1,97 @@ > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/bridge/ite,it6251.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: ITE IT6251 LVDS-to-eDP bridge bindings > + > +maintainers: > + - Marek Vasut <marex@denx.de> > + - Richard Marko <srk@48.io> > + > +description: | > + The IT6251 is a high-performance single-chip > + De-SSC LVDS to DisplayPort converter. > + Combined with LVDS receiver and DisplayPort Transmitter, > + the IT6251 supports LVDS input and DisplayPort 1.1a > + output by conversion function. You could reflow this to the 80 columns limit. It also sounds like marketing material copied from the datasheet, with "by conversion function" likely a bad translation. > + > +properties: > + compatible: > + const: ite,it6251 > + > + reg: > + items: > + - description: I2C address of the bridge > + - description: I2C address of the LVDS part > + > + reg-names: > + items: > + - const: bridge > + - const: lvds > + > + ports: > + type: object > + > + properties: > + "#address-cells": > + const: 1 > + > + "#size-cells": > + const: 0 > + > + port@0: > + type: object > + description: | > + Video port for eDP output (typically panel). > + > + port@1: > + type: object > + description: | > + Video port for LVDS input. We traditionally use port 0 for the input and port 1 for the output. I'd rather do the same here to remain consistent, and allow generic code to operate on this device. > + > + required: > + - port@0 > + - port@1 > + > + additionalProperties: false > + > + power-supply: true There are multiple power supplies for the chip, shouldn't we have multiple properties ? I would also name the properties according to the supply name. The chip has an HPD input. I would recommend already documenting an optional boolean no-hpd property to report when the HPD input is not connected. > + > +required: > + - compatible > + - reg > + - reg-names > + - power-supply > + - ports > + > +additionalProperties: false > + > +examples: > + - | > + it6251@5c { > + compatible = "ite,it6251"; > + reg = <0x5c>, <0x5e>; > + reg-names = "bridge", "lvds"; > + power-supply = <®_display>; > + > + ports { > + #address-cells = <1>; > + #size-cells = <0>; > + > + port@0 { > + reg = <0>; > + bridge_out_edp0: endpoint { > + remote-endpoint = <&panel_in_edp0>; > + }; > + }; > + > + port@1 { > + reg = <1>; > + bridge_in_lvds0: endpoint { > + remote-endpoint = <&lvds0_out>; > + }; > + }; > + }; > + }; -- Regards, Laurent Pinchart _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-09 13:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-09 11:17 [PATCH 0/2] Novena laptop: LVDS-to-eDP bridge srk 2020-05-09 11:17 ` srk 2020-05-09 11:17 ` [PATCH 1/2] dt-bindings: it6251: add bindings for IT6251 " srk 2020-05-09 11:17 ` srk 2020-05-09 13:44 ` Laurent Pinchart [this message] 2020-05-09 13:44 ` Laurent Pinchart 2020-05-11 10:15 ` Sam Ravnborg 2020-05-11 10:15 ` Sam Ravnborg 2020-05-09 11:17 ` [PATCH 2/2] drm/bridge: Add ITE IT6251 bridge driver srk 2020-05-09 11:17 ` srk 2020-05-09 13:48 ` Laurent Pinchart 2020-05-09 13:48 ` Laurent Pinchart 2020-05-11 10:29 ` Sam Ravnborg 2020-05-11 10:29 ` Sam Ravnborg
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200509134410.GA5946@pendragon.ideasonboard.com \ --to=laurent.pinchart@ideasonboard.com \ --cc=a.hajda@samsung.com \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=jernej.skrabec@siol.net \ --cc=jonas@kwiboo.se \ --cc=linux-kernel@vger.kernel.org \ --cc=lkundrak@v3.sk \ --cc=marex@denx.de \ --cc=narmstrong@baylibre.com \ --cc=robh+dt@kernel.org \ --cc=srk@48.io \ --cc=xobs@kosagi.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.