From: spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
To: Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ryadav-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
nganji-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
chandanu-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
Subject: Re: [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings
Date: Wed, 18 Apr 2018 23:38:32 +0530 [thread overview]
Message-ID: <6526809dc63f71f02982b6a57719e01a@codeaurora.org> (raw)
In-Reply-To: <20180418135842.GV73214@art_vandelay>
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 <spanda@codeaurora.org>
>> ---
>> .../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 0000000..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 = <&qe_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 = <&msmgpio 33 GPIO_ACTIVE_HIGH>;
>> +
>> + vccio-supply = <&pm8916_l17>;
>> + vcca-supply = <&pm8916_l6>;
>> +
>> + 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 {
>> + remote-endpoint = <&edp_panel_in>;
>> + };
>> + };
>> + };
>> +}
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>> Forum,
>> a Linux Foundation Collaborative Project
>>
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
next prev parent reply other threads:[~2018-04-18 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180419072054epcas5p364c0eae57d11ff5ff22890223a79c271@epcas5p3.samsung.com>
2018-04-18 12:19 ` [[RFC]DPU PATCH 0/4] Add suppport for sn65dsi86 bridge chip and Innolux 2k edp panel driver Sandeep Panda
[not found] ` <1524054002-17869-1-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-18 12:19 ` [[RFC]DPU PATCH 1/4] drm/bridge: add support for sn65dsi86 bridge driver Sandeep Panda
2018-04-18 14:11 ` Sean Paul
2018-04-18 18:31 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
2018-04-19 4:37 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
[not found] ` <1524054002-17869-2-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-19 15:14 ` Jordan Crouse
[not found] ` <20180419151438.GA18652-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-04-19 18:18 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
2018-04-18 12:20 ` [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings Sandeep Panda
2018-04-18 13:58 ` Sean Paul
2018-04-18 18:08 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ [this message]
2018-04-18 12:20 ` [[RFC]DPU PATCH 3/4] drm/panel: add Innolux TV123WAM eDP panel driver Sandeep Panda
2018-04-18 12:20 ` [[RFC]DPU PATCH 4/4] dt-bindings: Add Innolux TV123WAM panel bindings Sandeep Panda
2018-04-24 14:43 ` Rob Herring
2018-04-25 2:16 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
[not found] ` <cb59510635f0e7c010588a4603ae3f0f-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-25 14:40 ` Rob Herring
2018-04-18 14:12 ` [[RFC]DPU PATCH 0/4] Add suppport for sn65dsi86 bridge chip and Innolux 2k edp panel driver Sean Paul
2018-04-18 18:36 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
2018-04-26 7:08 ` Andrzej Hajda
2018-04-19 17:56 Sandeep Panda
[not found] ` <1524160568-27583-1-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-19 17:56 ` [[RFC]DPU PATCH 2/4] dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings Sandeep Panda
[not found] ` <1524160568-27583-3-git-send-email-spanda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-25 23:45 ` Stephen Boyd
[not found] ` <152469995691.46528.3834882157254635250-n1Xw8LXHxjTHt/MElyovVYaSKrA+ACpX0E9HWUfgJXw@public.gmane.org>
2018-04-26 0:46 ` Rob Clark
[not found] ` <CAF6AEGuWo9U5OU5nKSSwzRV_FWszTj_8S3Hns9hFHWBPsepnVw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-27 3:13 ` Rob Herring
2018-04-27 7:02 ` spanda-sgV2jX0FEOL9JmXXK+q4OQ
[not found] ` <0522b749900b3a54508abef6bd15252f-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-27 17:07 ` Rob Clark
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=6526809dc63f71f02982b6a57719e01a@codeaurora.org \
--to=spanda-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=chandanu-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=hoegsberg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nganji-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ryadav-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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.