From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: airlied@linux.ie, daniel@ffwll.ch, robh+dt@kernel.org,
narmstrong@baylibre.com, a.hajda@samsung.com,
spanda@codeaurora.org, 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,
Krzysztof Kozlowski <krzk@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Stephen Boyd <sboyd@kernel.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 23:31:03 +0300 [thread overview]
Message-ID: <20200415203103.GO4758@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200415084758.1.Ifcdc4ecb12742a27862744ee1e8753cb95a38a7f@changeid>
Hi Douglas,
Thank you for the patch.
On Wed, Apr 15, 2020 at 08:48:39AM -0700, Douglas Anderson wrote:
> 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.
You can also add your name ;-)
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
>
> .../bindings/display/bridge/ti,sn65dsi86.txt | 87 --------
> .../bindings/display/bridge/ti,sn65dsi86.yaml | 188 ++++++++++++++++++
> 2 files changed, 188 insertions(+), 87 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> deleted file mode 100644
> index 8ec4a7f2623a..000000000000
> --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> +++ /dev/null
> @@ -1,87 +0,0 @@
> -SN65DSI86 DSI to eDP bridge chip
> ---------------------------------
> -
> -This is the binding for Texas Instruments SN65DSI86 bridge.
> -http://www.ti.com/general/docs/lit/getliterature.tsp?genericPartNumber=sn65dsi86&fileType=pdf
> -
> -Required properties:
> -- compatible: Must be "ti,sn65dsi86"
> -- reg: i2c address of the chip, 0x2d as per datasheet
> -- enable-gpios: gpio specification for bridge_en pin (active high)
> -
> -- vccio-supply: A 1.8V supply that powers up the digital IOs.
> -- vpll-supply: A 1.8V supply that powers up the displayport PLL.
> -- vcca-supply: A 1.2V supply that powers up the analog circuits.
> -- vcc-supply: A 1.2V supply that powers up the digital core.
> -
> -Optional properties:
> -- interrupts-extended: Specifier for the SN65DSI86 interrupt line.
> -
> -- gpio-controller: Marks the device has a GPIO controller.
> -- #gpio-cells : Should be two. The first cell is the pin number and
> - the second cell is used to specify flags.
> - See ../../gpio/gpio.txt for more information.
> -- #pwm-cells : Should be one. See ../../pwm/pwm.yaml for description of
> - the cell formats.
> -
> -- clock-names: should be "refclk"
> -- clocks: Specification for input reference clock. The reference
> - clock rate must be 12 MHz, 19.2 MHz, 26 MHz, 27 MHz or 38.4 MHz.
> -
> -- data-lanes: See ../../media/video-interface.txt
> -- lane-polarities: See ../../media/video-interface.txt
> -
> -- suspend-gpios: specification for GPIO1 pin on bridge (active low)
Where has suspend-gpios gone ? :-)
> -
> -Required nodes:
> -This device has two video ports. Their connections are modelled using the
> -OF graph bindings specified in Documentation/devicetree/bindings/graph.txt.
> -
> -- Video port 0 for DSI input
> -- Video port 1 for eDP output
> -
> -Example
> --------
> -
> -edp-bridge@2d {
> - compatible = "ti,sn65dsi86";
> - #address-cells = <1>;
> - #size-cells = <0>;
> - reg = <0x2d>;
> -
> - enable-gpios = <&msmgpio 33 GPIO_ACTIVE_HIGH>;
> - suspend-gpios = <&msmgpio 34 GPIO_ACTIVE_LOW>;
> -
> - interrupts-extended = <&gpio3 4 IRQ_TYPE_EDGE_FALLING>;
> -
> - vccio-supply = <&pm8916_l17>;
> - vcca-supply = <&pm8916_l6>;
> - vpll-supply = <&pm8916_l17>;
> - vcc-supply = <&pm8916_l6>;
> -
> - clock-names = "refclk";
> - clocks = <&input_refclk>;
> -
> - ports {
> - #address-cells = <1>;
> - #size-cells = <0>;
> -
> - port@0 {
> - reg = <0>;
> -
> - edp_bridge_in: endpoint {
> - remote-endpoint = <&dsi_out>;
> - };
> - };
> -
> - port@1 {
> - reg = <1>;
> -
> - edp_bridge_out: endpoint {
> - data-lanes = <2 1 3 0>;
> - lane-polarities = <0 1 0 1>;
> - remote-endpoint = <&edp_panel_in>;
> - };
> - };
> - };
> -}
> 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).
> +
> + 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.
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> + description:
> + Specification for input reference clock. The reference clock rate must
> + be 12 MHz, 19.2 MHz, 26 MHz, 27 MHz or 38.4 MHz.
> +
> + clock-names:
> + const: refclk
> +
> + gpio-controller: true
> + '#gpio-cells':
> + const: 2
> + description:
> + First cell is pin number, second cell is flags. GPIO pin numbers are
> + 1-based to match the datasheet. See ../../gpio/gpio.txt for more
> + information.
> +
> + '#pwm-cells':
> + const: 1
> + description: See ../../pwm/pwm.yaml for description of the cell formats.
> +
> + data-lanes:
Should this have
minItems: 1
maxItems: 4
items:
enum:
- 0
- 1
- 2
- 3
> + description: See ../../media/video-interface.txt
> +
> + lane-polarities:
> + description: See ../../media/video-interface.txt
And something similar here,
minItems: 1
maxItems: 4
items:
enum:
- 0
- 1
uniqueItems: false
I'm not entirely sure where uniqueItems should be placed. I'm also not
sure how to specify that both data-lanes and lane-polarities need to
have the same number of items, maybe
dependencies:
data-lanes: [lane-polarities]
> +
> + 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:
If there's a single endpoint, you don't need patternProperties, it can
be specified in properties.
> + type: object
> + additionalProperties: false
> +
> + properties:
> + remote-endpoint: true
> +
> + required:
> + - reg
> +
> + port@1:
> + type: object
> + additionalProperties: false
> +
> + description:
> + Video port for eDP output (panel or connector).
> +
> + properties:
> + reg:
> + const: 1
> +
> + patternProperties:
> + endpoint:
Same here.
> + type: object
> + additionalProperties: false
> +
> + properties:
> + remote-endpoint: true
> +
> + required:
> + - reg
> +
> + required:
> + - "#address-cells"
> + - "#size-cells"
> + - port@0
> + - port@1
> +
> +required:
> + - compatible
> + - reg
> + - enable-gpios
> + - vccio-supply
> + - vpll-supply
> + - vcca-supply
> + - vcc-supply
> + - ports
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,rpmh.h>
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + bridge@2d {
> + compatible = "ti,sn65dsi86";
> + reg = <0x2d>;
> +
> + interrupt-parent = <&tlmm>;
> + interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
> +
> + enable-gpios = <&tlmm 102 GPIO_ACTIVE_HIGH>;
> +
> + vpll-supply = <&src_pp1800_s4a>;
> + vccio-supply = <&src_pp1800_s4a>;
> + vcca-supply = <&src_pp1200_l2a>;
> + vcc-supply = <&src_pp1200_l2a>;
> +
> + clocks = <&rpmhcc RPMH_LN_BB_CLK2>;
> + clock-names = "refclk";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + endpoint {
> + remote-endpoint = <&dsi0_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> + endpoint {
> + remote-endpoint = <&panel_in_edp>;
> + };
> + };
> + };
> + };
> + };
> +
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: robdclark@chromium.org, devicetree@vger.kernel.org,
jernej.skrabec@siol.net, Stephen Boyd <sboyd@kernel.org>,
narmstrong@baylibre.com, airlied@linux.ie,
linux-arm-msm@vger.kernel.org, jonas@kwiboo.se,
jeffrey.l.hugo@gmail.com, spanda@codeaurora.org,
dri-devel@lists.freedesktop.org, bjorn.andersson@linaro.org,
a.hajda@samsung.com, robh+dt@kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
swboyd@chromium.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 23:31:03 +0300 [thread overview]
Message-ID: <20200415203103.GO4758@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200415084758.1.Ifcdc4ecb12742a27862744ee1e8753cb95a38a7f@changeid>
Hi Douglas,
Thank you for the patch.
On Wed, Apr 15, 2020 at 08:48:39AM -0700, Douglas Anderson wrote:
> 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.
You can also add your name ;-)
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
>
> .../bindings/display/bridge/ti,sn65dsi86.txt | 87 --------
> .../bindings/display/bridge/ti,sn65dsi86.yaml | 188 ++++++++++++++++++
> 2 files changed, 188 insertions(+), 87 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> deleted file mode 100644
> index 8ec4a7f2623a..000000000000
> --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> +++ /dev/null
> @@ -1,87 +0,0 @@
> -SN65DSI86 DSI to eDP bridge chip
> ---------------------------------
> -
> -This is the binding for Texas Instruments SN65DSI86 bridge.
> -http://www.ti.com/general/docs/lit/getliterature.tsp?genericPartNumber=sn65dsi86&fileType=pdf
> -
> -Required properties:
> -- compatible: Must be "ti,sn65dsi86"
> -- reg: i2c address of the chip, 0x2d as per datasheet
> -- enable-gpios: gpio specification for bridge_en pin (active high)
> -
> -- vccio-supply: A 1.8V supply that powers up the digital IOs.
> -- vpll-supply: A 1.8V supply that powers up the displayport PLL.
> -- vcca-supply: A 1.2V supply that powers up the analog circuits.
> -- vcc-supply: A 1.2V supply that powers up the digital core.
> -
> -Optional properties:
> -- interrupts-extended: Specifier for the SN65DSI86 interrupt line.
> -
> -- gpio-controller: Marks the device has a GPIO controller.
> -- #gpio-cells : Should be two. The first cell is the pin number and
> - the second cell is used to specify flags.
> - See ../../gpio/gpio.txt for more information.
> -- #pwm-cells : Should be one. See ../../pwm/pwm.yaml for description of
> - the cell formats.
> -
> -- clock-names: should be "refclk"
> -- clocks: Specification for input reference clock. The reference
> - clock rate must be 12 MHz, 19.2 MHz, 26 MHz, 27 MHz or 38.4 MHz.
> -
> -- data-lanes: See ../../media/video-interface.txt
> -- lane-polarities: See ../../media/video-interface.txt
> -
> -- suspend-gpios: specification for GPIO1 pin on bridge (active low)
Where has suspend-gpios gone ? :-)
> -
> -Required nodes:
> -This device has two video ports. Their connections are modelled using the
> -OF graph bindings specified in Documentation/devicetree/bindings/graph.txt.
> -
> -- Video port 0 for DSI input
> -- Video port 1 for eDP output
> -
> -Example
> --------
> -
> -edp-bridge@2d {
> - compatible = "ti,sn65dsi86";
> - #address-cells = <1>;
> - #size-cells = <0>;
> - reg = <0x2d>;
> -
> - enable-gpios = <&msmgpio 33 GPIO_ACTIVE_HIGH>;
> - suspend-gpios = <&msmgpio 34 GPIO_ACTIVE_LOW>;
> -
> - interrupts-extended = <&gpio3 4 IRQ_TYPE_EDGE_FALLING>;
> -
> - vccio-supply = <&pm8916_l17>;
> - vcca-supply = <&pm8916_l6>;
> - vpll-supply = <&pm8916_l17>;
> - vcc-supply = <&pm8916_l6>;
> -
> - clock-names = "refclk";
> - clocks = <&input_refclk>;
> -
> - ports {
> - #address-cells = <1>;
> - #size-cells = <0>;
> -
> - port@0 {
> - reg = <0>;
> -
> - edp_bridge_in: endpoint {
> - remote-endpoint = <&dsi_out>;
> - };
> - };
> -
> - port@1 {
> - reg = <1>;
> -
> - edp_bridge_out: endpoint {
> - data-lanes = <2 1 3 0>;
> - lane-polarities = <0 1 0 1>;
> - remote-endpoint = <&edp_panel_in>;
> - };
> - };
> - };
> -}
> 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).
> +
> + 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.
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> + description:
> + Specification for input reference clock. The reference clock rate must
> + be 12 MHz, 19.2 MHz, 26 MHz, 27 MHz or 38.4 MHz.
> +
> + clock-names:
> + const: refclk
> +
> + gpio-controller: true
> + '#gpio-cells':
> + const: 2
> + description:
> + First cell is pin number, second cell is flags. GPIO pin numbers are
> + 1-based to match the datasheet. See ../../gpio/gpio.txt for more
> + information.
> +
> + '#pwm-cells':
> + const: 1
> + description: See ../../pwm/pwm.yaml for description of the cell formats.
> +
> + data-lanes:
Should this have
minItems: 1
maxItems: 4
items:
enum:
- 0
- 1
- 2
- 3
> + description: See ../../media/video-interface.txt
> +
> + lane-polarities:
> + description: See ../../media/video-interface.txt
And something similar here,
minItems: 1
maxItems: 4
items:
enum:
- 0
- 1
uniqueItems: false
I'm not entirely sure where uniqueItems should be placed. I'm also not
sure how to specify that both data-lanes and lane-polarities need to
have the same number of items, maybe
dependencies:
data-lanes: [lane-polarities]
> +
> + 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:
If there's a single endpoint, you don't need patternProperties, it can
be specified in properties.
> + type: object
> + additionalProperties: false
> +
> + properties:
> + remote-endpoint: true
> +
> + required:
> + - reg
> +
> + port@1:
> + type: object
> + additionalProperties: false
> +
> + description:
> + Video port for eDP output (panel or connector).
> +
> + properties:
> + reg:
> + const: 1
> +
> + patternProperties:
> + endpoint:
Same here.
> + type: object
> + additionalProperties: false
> +
> + properties:
> + remote-endpoint: true
> +
> + required:
> + - reg
> +
> + required:
> + - "#address-cells"
> + - "#size-cells"
> + - port@0
> + - port@1
> +
> +required:
> + - compatible
> + - reg
> + - enable-gpios
> + - vccio-supply
> + - vpll-supply
> + - vcca-supply
> + - vcc-supply
> + - ports
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,rpmh.h>
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + bridge@2d {
> + compatible = "ti,sn65dsi86";
> + reg = <0x2d>;
> +
> + interrupt-parent = <&tlmm>;
> + interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
> +
> + enable-gpios = <&tlmm 102 GPIO_ACTIVE_HIGH>;
> +
> + vpll-supply = <&src_pp1800_s4a>;
> + vccio-supply = <&src_pp1800_s4a>;
> + vcca-supply = <&src_pp1200_l2a>;
> + vcc-supply = <&src_pp1200_l2a>;
> +
> + clocks = <&rpmhcc RPMH_LN_BB_CLK2>;
> + clock-names = "refclk";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + endpoint {
> + remote-endpoint = <&dsi0_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> + endpoint {
> + remote-endpoint = <&panel_in_edp>;
> + };
> + };
> + };
> + };
> + };
> +
--
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-04-15 20:31 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 ` [PATCH 1/3] dt-bindings: drm/bridge: ti-sn65dsi86: Convert to yaml Stephen Boyd
2020-04-15 19:50 ` Stephen Boyd
2020-04-15 20:31 ` Laurent Pinchart [this message]
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=20200415203103.GO4758@pendragon.ideasonboard.com \
--to=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=sboyd@kernel.org \
--cc=spanda@codeaurora.org \
--cc=swboyd@chromium.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: link
Be 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.