Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-27 Thread Rob Clark 
On Fri, Apr 27, 2018 at 3:02 AM,   wrote:
> On 2018-04-27 08:43, Rob Herring wrote:
>>
>> On Wed, Apr 25, 2018 at 08:46:13PM -0400, Rob Clark wrote:
>>>
>>> On Wed, Apr 25, 2018 at 7:45 PM, Stephen Boyd 
>>> wrote:
>>> > Quoting Sandeep Panda (2018-04-19 10:56:06)
>>> >> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
>>> >>
>>> >> Changes in v1:
>>> >>  - Rephrase the dt-binding descriptions to be more inline with
>>> >> existing
>>> >>bindings (Andrzej Hajda).
>>> >>  - Add missing dt-binding that are parsed by corresponding driver
>>> >>(Andrzej Hajda).
>>> >>
>>> >> Changes in v2:
>>> >>  - Removed edp panel specific dt-binding entries. Only keep bridge
>>> >>specific entries (Sean Paul).
>>> >>  - Remove custom-modes dt entry since its usage is removed from driver
>>> >> also (Sean Paul).
>>> >>  - Remove is-pluggable dt entry since this will not be needed anymore
>>> >> (Sean Paul).
>>> >>
>>> >> Changes in v3:
>>> >>  - Removed irq-gpio dt entry and instead populate is an interrupt
>>> >>property (Rob Herring).
>>> >
>>> > These changelogs usually go below the triple dash, but maybe drm is
>>> > different and wants them?
>>>
>>> yeah, drm generally wants them in the commit msg rather than below the
>>> triple-dash, although I guess for bindings docs it should follow the
>>> rules for that tree.. I usually just fix up these sort of things as I
>>> apply patches, but not sure what other maintainers prefer
>>
>>
>> Well, these DPU patches aren't targeted for upstream so who cares.
>
>
> This change is independent of other DPU patches. We are planning to upstream
> these bridge and panel changes.
> I will upload the next patchset dropping the DPU tag to avoid any confusion.
>

jfwiw, probably a good idea not to use the 'DPU' tag for anything that
isn't dependent on the DPU patcheset, to reduce confusion

BR,
-R
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-27 Thread spanda 

On 2018-04-27 08:43, Rob Herring wrote:

On Wed, Apr 25, 2018 at 08:46:13PM -0400, Rob Clark wrote:
On Wed, Apr 25, 2018 at 7:45 PM, Stephen Boyd  
wrote:

> Quoting Sandeep Panda (2018-04-19 10:56:06)
>> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
>>
>> Changes in v1:
>>  - Rephrase the dt-binding descriptions to be more inline with existing
>>bindings (Andrzej Hajda).
>>  - Add missing dt-binding that are parsed by corresponding driver
>>(Andrzej Hajda).
>>
>> Changes in v2:
>>  - Removed edp panel specific dt-binding entries. Only keep bridge
>>specific entries (Sean Paul).
>>  - Remove custom-modes dt entry since its usage is removed from driver also 
(Sean Paul).
>>  - Remove is-pluggable dt entry since this will not be needed anymore (Sean 
Paul).
>>
>> Changes in v3:
>>  - Removed irq-gpio dt entry and instead populate is an interrupt
>>property (Rob Herring).
>
> These changelogs usually go below the triple dash, but maybe drm is
> different and wants them?

yeah, drm generally wants them in the commit msg rather than below the
triple-dash, although I guess for bindings docs it should follow the
rules for that tree.. I usually just fix up these sort of things as I
apply patches, but not sure what other maintainers prefer


Well, these DPU patches aren't targeted for upstream so who cares.


This change is independent of other DPU patches. We are planning to 
upstream these bridge and panel changes.
I will upload the next patchset dropping the DPU tag to avoid any 
confusion.


Many patch revision changelogs I see are crap with statements like
"implement changes requested by ??". But in this case, the changelog is
really good.

Rob

___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-26 Thread Rob Herring 
On Wed, Apr 25, 2018 at 08:46:13PM -0400, Rob Clark wrote:
> On Wed, Apr 25, 2018 at 7:45 PM, Stephen Boyd  wrote:
> > Quoting Sandeep Panda (2018-04-19 10:56:06)
> >> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
> >>
> >> Changes in v1:
> >>  - Rephrase the dt-binding descriptions to be more inline with existing
> >>bindings (Andrzej Hajda).
> >>  - Add missing dt-binding that are parsed by corresponding driver
> >>(Andrzej Hajda).
> >>
> >> Changes in v2:
> >>  - Removed edp panel specific dt-binding entries. Only keep bridge
> >>specific entries (Sean Paul).
> >>  - Remove custom-modes dt entry since its usage is removed from driver 
> >> also (Sean Paul).
> >>  - Remove is-pluggable dt entry since this will not be needed anymore 
> >> (Sean Paul).
> >>
> >> Changes in v3:
> >>  - Removed irq-gpio dt entry and instead populate is an interrupt
> >>property (Rob Herring).
> >
> > These changelogs usually go below the triple dash, but maybe drm is
> > different and wants them?
> 
> yeah, drm generally wants them in the commit msg rather than below the
> triple-dash, although I guess for bindings docs it should follow the
> rules for that tree.. I usually just fix up these sort of things as I
> apply patches, but not sure what other maintainers prefer

Well, these DPU patches aren't targeted for upstream so who cares.

Many patch revision changelogs I see are crap with statements like 
"implement changes requested by ??". But in this case, the changelog is 
really good.

Rob
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-26 Thread Stephen Boyd 
Quoting Sandeep Panda (2018-04-19 10:56:06)
> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
> 
> Changes in v1:
>  - Rephrase the dt-binding descriptions to be more inline with existing
>bindings (Andrzej Hajda).
>  - Add missing dt-binding that are parsed by corresponding driver
>(Andrzej Hajda).
> 
> Changes in v2:
>  - Removed edp panel specific dt-binding entries. Only keep bridge
>specific entries (Sean Paul).
>  - Remove custom-modes dt entry since its usage is removed from driver also 
> (Sean Paul).
>  - Remove is-pluggable dt entry since this will not be needed anymore (Sean 
> Paul).
> 
> Changes in v3:
>  - Removed irq-gpio dt entry and instead populate is an interrupt
>property (Rob Herring).

These changelogs usually go below the triple dash, but maybe drm is
different and wants them?

> 
> Signed-off-by: Sandeep Panda 
> ---
>  .../bindings/display/bridge/ti,sn65dsi86.txt   | 61 
> ++
>  1 file changed, 61 insertions(+)
>  create mode 100644 
> Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> 
> diff --git 
> a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt 
> b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> new file mode 100644
> index 000..412c4a2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> @@ -0,0 +1,61 @@
> +SN65DSI86 DSI to eDP bridge chip
> +
> +
> +This is the binding for Texas Instruments SN65DSI86 bridge.

Can you add a link to the datasheet here please?

> +
> +Required properties:
> +- compatible: Must be "ti,sn65dsi86"
> +- reg: i2c address of the chip, 0x2d as per datasheet
> +- enable-gpios: OF device-tree gpio specifications for bridge_en pin
> +
> +- vccio-supply: A 1.8V supply that powers up the digital IOs.
> +- vcca-supply: A 1.2V supply that powers up the analog circuits.

Can you add vpll and vcc from the datasheet as well?

Also refclk would be good to have just in case it's present (so
optional?), and hpd should be another gpio property (could be optional I
suppose).

It also looks like this chip has a gpio controller on it, so it would
need to have a gpio-controller property and #gpio-cells. And one of
those GPIOs does PWM, so it would need #pwm-cells as well. I'm not
saying the code needs to be written yet, but at least the binding would
need to specify these things.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-25 Thread Rob Clark 
On Wed, Apr 25, 2018 at 7:45 PM, Stephen Boyd  wrote:
> Quoting Sandeep Panda (2018-04-19 10:56:06)
>> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
>>
>> Changes in v1:
>>  - Rephrase the dt-binding descriptions to be more inline with existing
>>bindings (Andrzej Hajda).
>>  - Add missing dt-binding that are parsed by corresponding driver
>>(Andrzej Hajda).
>>
>> Changes in v2:
>>  - Removed edp panel specific dt-binding entries. Only keep bridge
>>specific entries (Sean Paul).
>>  - Remove custom-modes dt entry since its usage is removed from driver also 
>> (Sean Paul).
>>  - Remove is-pluggable dt entry since this will not be needed anymore (Sean 
>> Paul).
>>
>> Changes in v3:
>>  - Removed irq-gpio dt entry and instead populate is an interrupt
>>property (Rob Herring).
>
> These changelogs usually go below the triple dash, but maybe drm is
> different and wants them?

yeah, drm generally wants them in the commit msg rather than below the
triple-dash, although I guess for bindings docs it should follow the
rules for that tree.. I usually just fix up these sort of things as I
apply patches, but not sure what other maintainers prefer

BR,
-R

>>
>> Signed-off-by: Sandeep Panda 
>> ---
>>  .../bindings/display/bridge/ti,sn65dsi86.txt   | 61 
>> ++
>>  1 file changed, 61 insertions(+)
>>  create mode 100644 
>> Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
>>
>> diff --git 
>> a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt 
>> b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
>> new file mode 100644
>> index 000..412c4a2
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
>> @@ -0,0 +1,61 @@
>> +SN65DSI86 DSI to eDP bridge chip
>> +
>> +
>> +This is the binding for Texas Instruments SN65DSI86 bridge.
>
> Can you add a link to the datasheet here please?
>
>> +
>> +Required properties:
>> +- compatible: Must be "ti,sn65dsi86"
>> +- reg: i2c address of the chip, 0x2d as per datasheet
>> +- enable-gpios: OF device-tree gpio specifications for bridge_en pin
>> +
>> +- vccio-supply: A 1.8V supply that powers up the digital IOs.
>> +- vcca-supply: A 1.2V supply that powers up the analog circuits.
>
> Can you add vpll and vcc from the datasheet as well?
>
> Also refclk would be good to have just in case it's present (so
> optional?), and hpd should be another gpio property (could be optional I
> suppose).
>
> It also looks like this chip has a gpio controller on it, so it would
> need to have a gpio-controller property and #gpio-cells. And one of
> those GPIOs does PWM, so it would need #pwm-cells as well. I'm not
> saying the code needs to be written yet, but at least the binding would
> need to specify these things.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-20 Thread Sandeep Panda 
Document the bindings used for the sn65dsi86 DSI to eDP bridge.

Changes in v1:
 - Rephrase the dt-binding descriptions to be more inline with existing
   bindings (Andrzej Hajda).
 - Add missing dt-binding that are parsed by corresponding driver
   (Andrzej Hajda).

Changes in v2:
 - Removed edp panel specific dt-binding entries. Only keep bridge
   specific entries (Sean Paul).
 - Remove custom-modes dt entry since its usage is removed from driver also 
(Sean Paul).
 - Remove is-pluggable dt entry since this will not be needed anymore (Sean 
Paul).

Changes in v3:
 - Removed irq-gpio dt entry and instead populate is an interrupt
   property (Rob Herring).

Signed-off-by: Sandeep Panda 
---
 .../bindings/display/bridge/ti,sn65dsi86.txt   | 61 ++
 1 file changed, 61 insertions(+)
 create mode 100644 
Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt

diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt 
b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
new file mode 100644
index 000..412c4a2
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
@@ -0,0 +1,61 @@
+SN65DSI86 DSI to eDP bridge chip
+
+
+This is the binding for Texas Instruments SN65DSI86 bridge.
+
+Required properties:
+- compatible: Must be "ti,sn65dsi86"
+- reg: i2c address of the chip, 0x2d as per datasheet
+- enable-gpios: OF device-tree gpio specifications for bridge_en pin
+
+- vccio-supply: A 1.8V supply that powers up the digital IOs.
+- vcca-supply: A 1.2V supply that powers up the analog circuits.
+
+Optional properties:
+- interrupts: Specifier for the SN65DSI86 interrupt line.
+
+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 = < 33 GPIO_ACTIVE_HIGH>;
+   interrupt-parent = <>;
+   interrupts = <4 IRQ_TYPE_EDGE_FALLING>;
+
+   vccio-supply = <_l17>;
+   vcca-supply = <_l6>;
+
+   ports {
+   #address-cells = <1>;
+   #size-cells = <0>;
+
+   port@0 {
+   reg = <0>;
+
+   edp_bridge_in: endpoint {
+   remote-endpoint = <_out>;
+   };
+   };
+
+   port@1 {
+   reg = <1>;
+
+   edp_bridge_out: endpoint {
+   remote-endpoint = <_panel_in>;
+   };
+   };
+   };
+}
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-19 Thread Sandeep Panda 
Document the bindings used for the sn65dsi86 DSI to eDP bridge.

Signed-off-by: Sandeep Panda 
---
 .../bindings/display/bridge/ti,sn65dsi86.txt   | 60 ++
 1 file changed, 60 insertions(+)
 create mode 100644 
Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt

diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt 
b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
new file mode 100644
index 000..9e2612e
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
@@ -0,0 +1,60 @@
+SN65DSI86 DSI to eDP bridge chip
+
+
+This is the binding for Texas Instruments SN65DSI86 bridge.
+
+Required properties:
+- compatible: Must be "ti,sn65dsi86"
+- reg: i2c address of the chip, 0x2d as per datasheet
+- enable-gpios: OF device-tree gpio specifications for bridge_en pin
+
+- vccio-supply: A 1.8V supply that powers up the digital IOs.
+- vcca-supply: A 1.2V supply that powers up the analog circuits.
+
+Optional properties:
+
+- irq-gpios: OF device-tree gpio specification for interrupt pin
+
+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 = < 33 GPIO_ACTIVE_HIGH>;
+
+   vccio-supply = <_l17>;
+   vcca-supply = <_l6>;
+
+   ports {
+   #address-cells = <1>;
+   #size-cells = <0>;
+
+   port@0 {
+   reg = <0>;
+
+   edp_bridge_in: endpoint {
+   remote-endpoint = <_out>;
+   };
+   };
+
+   port@1 {
+   reg = <1>;
+
+   edp_bridge_out: endpoint {
+   remote-endpoint = <_panel_in>;
+   };
+   };
+   };
+}
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-19 Thread spanda 

On 2018-04-18 19:28, Sean Paul wrote:

On Wed, Apr 18, 2018 at 05:50:00PM +0530, Sandeep Panda wrote:

Document the bindings used for the sn65dsi86 DSI to eDP bridge.



Please add a changelog to your patches so reviewers know what has 
changed

between patch versions.

I will update the change log in the commit text of the patches.



Signed-off-by: Sandeep Panda 
---
 .../bindings/display/bridge/ti,sn65dsi86.txt   | 60 
++

 1 file changed, 60 insertions(+)
 create mode 100644 
Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt


diff --git 
a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt 
b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt

new file mode 100644
index 000..9e2612e
--- /dev/null
+++ 
b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt

@@ -0,0 +1,60 @@
+SN65DSI86 DSI to eDP bridge chip
+
+
+This is the binding for Texas Instruments SN65DSI86 bridge.
+
+Required properties:
+- compatible: Must be "ti,sn65dsi86"
+- reg: i2c address of the chip, 0x2d as per datasheet
+- enable-gpios: OF device-tree gpio specifications for bridge_en pin


The datasheet only has one enable pin, why gpios?

This is the convention followed by other bridge drivers also.
https://www.kernel.org/doc/Documentation/devicetree/bindings/gpio/gpio.txt
please the example mentioned here,
Example of a node using GPIOs:

node {
enable-gpios = <_pio_e 18 GPIO_ACTIVE_HIGH>;
};




+
+- vccio-supply: A 1.8V supply that powers up the digital IOs.
+- vcca-supply: A 1.2V supply that powers up the analog circuits.
+
+Optional properties:
+
+- irq-gpios: OF device-tree gpio specification for interrupt pin


From the last review, Rob said, 'Use "interrupts" property instead.'

You didn't provide responses to prior review comments, so it's unclear 
whether

you've intentionally or unintentionally ignored him :)

Sorry missed it completely while addressing other review comments.


Sean


+
+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 = < 33 GPIO_ACTIVE_HIGH>;
+
+   vccio-supply = <_l17>;
+   vcca-supply = <_l6>;
+
+   ports {
+   #address-cells = <1>;
+   #size-cells = <0>;
+
+   port@0 {
+   reg = <0>;
+
+   edp_bridge_in: endpoint {
+   remote-endpoint = <_out>;
+   };
+   };
+
+   port@1 {
+   reg = <1>;
+
+   edp_bridge_out: endpoint {
+   remote-endpoint = <_panel_in>;
+   };
+   };
+   };
+}
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,

a Linux Foundation Collaborative Project


___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings

2018-04-18 Thread Sean Paul 
On Wed, Apr 18, 2018 at 05:50:00PM +0530, Sandeep Panda wrote:
> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
> 

Please add a changelog to your patches so reviewers know what has changed
between patch versions. 

> Signed-off-by: Sandeep Panda 
> ---
>  .../bindings/display/bridge/ti,sn65dsi86.txt   | 60 
> ++
>  1 file changed, 60 insertions(+)
>  create mode 100644 
> Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> 
> diff --git 
> a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt 
> b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> new file mode 100644
> index 000..9e2612e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
> @@ -0,0 +1,60 @@
> +SN65DSI86 DSI to eDP bridge chip
> +
> +
> +This is the binding for Texas Instruments SN65DSI86 bridge.
> +
> +Required properties:
> +- compatible: Must be "ti,sn65dsi86"
> +- reg: i2c address of the chip, 0x2d as per datasheet
> +- enable-gpios: OF device-tree gpio specifications for bridge_en pin

The datasheet only has one enable pin, why gpios?

> +
> +- vccio-supply: A 1.8V supply that powers up the digital IOs.
> +- vcca-supply: A 1.2V supply that powers up the analog circuits.
> +
> +Optional properties:
> +
> +- irq-gpios: OF device-tree gpio specification for interrupt pin

From the last review, Rob said, 'Use "interrupts" property instead.'

You didn't provide responses to prior review comments, so it's unclear whether
you've intentionally or unintentionally ignored him :)

Sean

> +
> +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 = < 33 GPIO_ACTIVE_HIGH>;
> +
> + vccio-supply = <_l17>;
> + vcca-supply = <_l6>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> +
> + edp_bridge_in: endpoint {
> + remote-endpoint = <_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> +
> + edp_bridge_out: endpoint {
> + remote-endpoint = <_panel_in>;
> + };
> + };
> + };
> +}
> -- 
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
> 

-- 
Sean Paul, Software Engineer, Google / Chromium OS
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel