From: Stephen Boyd <swboyd@chromium.org> To: Douglas Anderson <dianders@chromium.org>, Laurent.pinchart@ideasonboard.com, a.hajda@samsung.com, airlied@linux.ie, daniel@ffwll.ch, narmstrong@baylibre.com, robh+dt@kernel.org, spanda@codeaurora.org Cc: jonas@kwiboo.se, bjorn.andersson@linaro.org, devicetree@vger.kernel.org, jeffrey.l.hugo@gmail.com, swboyd@chromium.org, jernej.skrabec@siol.net, linux-arm-msm@vger.kernel.org, robdclark@chromium.org, dri-devel@lists.freedesktop.org, Douglas Anderson <dianders@chromium.org>, Krzysztof Kozlowski <krzk@kernel.org>, Paul Walmsley <paul.walmsley@sifive.com>, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] dt-bindings: drm/bridge: ti-sn65dsi86: Convert to yaml Date: Wed, 15 Apr 2020 12:50:10 -0700 [thread overview] Message-ID: <158698021097.105027.12960498982161983978@swboyd.mtv.corp.google.com> (raw) In-Reply-To: <20200415084758.1.Ifcdc4ecb12742a27862744ee1e8753cb95a38a7f@changeid> Quoting Douglas Anderson (2020-04-15 08:48:39) > This moves the bindings over, based a lot on toshiba,tc358768.yaml. > Unless there's someone known to be better, I've set the maintainer in > the yaml as the first person to submit bindings. > > Signed-off-by: Douglas Anderson <dianders@chromium.org> > --- Awesome! > diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > new file mode 100644 > index 000000000000..8cacc6db33a9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > @@ -0,0 +1,188 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/bridge/ti,sn65dsi86.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: SN65DSI86 DSI to eDP bridge chip > + > +maintainers: > + - Sandeep Panda <spanda@codeaurora.org> > + > +description: | > + The Texas Instruments SN65DSI86 bridge takes MIPI DSI in and outputs eDP. > + http://www.ti.com/general/docs/lit/getliterature.tsp?genericPartNumber=sn65dsi86&fileType=pdf > + > +properties: > + compatible: > + const: ti,sn65dsi86 > + > + reg: > + const: 0x2d > + > + enable-gpios: > + maxItems: 1 > + description: GPIO specification for bridge_en pin (active high). s/specification/specifier/ ? I know the previous binding said specification but I don't know what that is. It's a specifier. > + > + vccio-supply: > + description: A 1.8V supply that powers up the digital IOs. > + > + vpll-supply: > + description: A 1.8V supply that powers up the DisplayPort PLL. > + > + vcca-supply: > + description: A 1.2V supply that powers up the analog circuits. > + > + vcc-supply: > + description: A 1.2V supply that powers up the digital core. Nitpick: Can we remove 'up' from these descriptions? > + > + interrupts: > + maxItems: 1 > + > + clocks: > + maxItems: 1 > + description: > + Specification for input reference clock. The reference clock rate must Clock specifier for input reference clock? > + be 12 MHz, 19.2 MHz, 26 MHz, 27 MHz or 38.4 MHz. > + > + clock-names: > + const: refclk > +
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <swboyd@chromium.org> To: Douglas Anderson <dianders@chromium.org>, Laurent.pinchart@ideasonboard.com, a.hajda@samsung.com, airlied@linux.ie, daniel@ffwll.ch, narmstrong@baylibre.com, robh+dt@kernel.org, spanda@codeaurora.org Cc: robdclark@chromium.org, devicetree@vger.kernel.org, jernej.skrabec@siol.net, jeffrey.l.hugo@gmail.com, linux-arm-msm@vger.kernel.org, jonas@kwiboo.se, Douglas Anderson <dianders@chromium.org>, dri-devel@lists.freedesktop.org, swboyd@chromium.org, Krzysztof Kozlowski <krzk@kernel.org>, Paul Walmsley <paul.walmsley@sifive.com>, bjorn.andersson@linaro.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] dt-bindings: drm/bridge: ti-sn65dsi86: Convert to yaml Date: Wed, 15 Apr 2020 12:50:10 -0700 [thread overview] Message-ID: <158698021097.105027.12960498982161983978@swboyd.mtv.corp.google.com> (raw) In-Reply-To: <20200415084758.1.Ifcdc4ecb12742a27862744ee1e8753cb95a38a7f@changeid> Quoting Douglas Anderson (2020-04-15 08:48:39) > This moves the bindings over, based a lot on toshiba,tc358768.yaml. > Unless there's someone known to be better, I've set the maintainer in > the yaml as the first person to submit bindings. > > Signed-off-by: Douglas Anderson <dianders@chromium.org> > --- Awesome! > diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > new file mode 100644 > index 000000000000..8cacc6db33a9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > @@ -0,0 +1,188 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/bridge/ti,sn65dsi86.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: SN65DSI86 DSI to eDP bridge chip > + > +maintainers: > + - Sandeep Panda <spanda@codeaurora.org> > + > +description: | > + The Texas Instruments SN65DSI86 bridge takes MIPI DSI in and outputs eDP. > + http://www.ti.com/general/docs/lit/getliterature.tsp?genericPartNumber=sn65dsi86&fileType=pdf > + > +properties: > + compatible: > + const: ti,sn65dsi86 > + > + reg: > + const: 0x2d > + > + enable-gpios: > + maxItems: 1 > + description: GPIO specification for bridge_en pin (active high). s/specification/specifier/ ? I know the previous binding said specification but I don't know what that is. It's a specifier. > + > + vccio-supply: > + description: A 1.8V supply that powers up the digital IOs. > + > + vpll-supply: > + description: A 1.8V supply that powers up the DisplayPort PLL. > + > + vcca-supply: > + description: A 1.2V supply that powers up the analog circuits. > + > + vcc-supply: > + description: A 1.2V supply that powers up the digital core. Nitpick: Can we remove 'up' from these descriptions? > + > + interrupts: > + maxItems: 1 > + > + clocks: > + maxItems: 1 > + description: > + Specification for input reference clock. The reference clock rate must Clock specifier for input reference clock? > + be 12 MHz, 19.2 MHz, 26 MHz, 27 MHz or 38.4 MHz. > + > + clock-names: > + const: refclk > + _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-15 19:50 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-15 15:48 [PATCH 1/3] dt-bindings: drm/bridge: ti-sn65dsi86: Convert to yaml Douglas Anderson 2020-04-15 15:48 ` Douglas Anderson 2020-04-15 15:48 ` [PATCH 2/3] dt-bindings: drm/bridge: ti-sn65dsi86: Add hpd-gpios to the bindings Douglas Anderson 2020-04-15 15:48 ` Douglas Anderson 2020-04-15 19:53 ` Stephen Boyd 2020-04-15 19:53 ` Stephen Boyd 2020-04-15 20:32 ` Laurent Pinchart 2020-04-15 20:32 ` Laurent Pinchart 2020-04-15 23:49 ` Doug Anderson 2020-04-15 23:49 ` Doug Anderson 2020-04-16 0:54 ` Laurent Pinchart 2020-04-16 0:54 ` Laurent Pinchart 2020-04-16 21:53 ` Doug Anderson 2020-04-16 21:53 ` Doug Anderson 2020-04-17 18:08 ` Laurent Pinchart 2020-04-17 18:08 ` Laurent Pinchart 2020-04-21 5:10 ` Doug Anderson 2020-04-21 5:10 ` Doug Anderson 2020-04-15 15:48 ` [PATCH 3/3] drm/bridge: ti-sn65dsi86: Allow one of the bridge GPIOs to be HPD Douglas Anderson 2020-04-15 15:48 ` Douglas Anderson 2020-04-15 19:50 ` Stephen Boyd [this message] 2020-04-15 19:50 ` [PATCH 1/3] dt-bindings: drm/bridge: ti-sn65dsi86: Convert to yaml Stephen Boyd 2020-04-15 20:31 ` Laurent Pinchart 2020-04-15 20:31 ` Laurent Pinchart 2020-04-21 5:07 ` Doug Anderson 2020-04-21 5:07 ` Doug Anderson
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=158698021097.105027.12960498982161983978@swboyd.mtv.corp.google.com \ --to=swboyd@chromium.org \ --cc=Laurent.pinchart@ideasonboard.com \ --cc=a.hajda@samsung.com \ --cc=airlied@linux.ie \ --cc=bjorn.andersson@linaro.org \ --cc=daniel@ffwll.ch \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=jeffrey.l.hugo@gmail.com \ --cc=jernej.skrabec@siol.net \ --cc=jonas@kwiboo.se \ --cc=krzk@kernel.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=narmstrong@baylibre.com \ --cc=paul.walmsley@sifive.com \ --cc=robdclark@chromium.org \ --cc=robh+dt@kernel.org \ --cc=spanda@codeaurora.org \ /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.