devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CK Hu <ck.hu@mediatek.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	"; Pawel Moll" <pawel.moll@arm.com>,
	Kumar Gala <galak@codeaurora.org>,
	"; David Airlie" <airlied@linux.ie>,
	Matthias, "Jitao Shi  <jitao.shi@mediatek.com>,
	; Thierry Reding" <treding@nvidia.com>,
	"; Ajay Kumar" <ajaykumar.rs@samsung.com>,
	"; Inki Dae" <inki.dae@samsung.com>,
	Rahul, "Sean Paul  <seanpaul@chromium.org>,
	; Vincent Palatin" <vpalatin@chromium.org>,
	"; Andy Yan" <andy.yan@rock-chips.com>,
	"; Philipp Zabel" <p.zabel@pengutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
	Sascha, Yingjoe, Eddie Huang <eddie.huang@mediatek.com>,
	"; Cawa Cheng" <cawa.cheng@mediatek.com>
Subject: RE: [RFC 1/2] Dcumentation: bridge: Add documentation for ps8640 DT properties
Date: Tue, 20 Oct 2015 14:12:16 +0800	[thread overview]
Message-ID: <1445321536.19417.5.camel@mtksdaap41> (raw)

Hi, Mark:

> -----Original Message-----
> From: Mark Rutland [mailto:mark.rutland@arm.com]
> Sent: Friday, October 16, 2015 9:05 PM
> > +++ b/Documentation/devicetree/bindings/video/bridge/ps8640.txt
> > @@ -0,0 +1,48 @@
> > +ps8640-bridge bindings
> > +
> > +Required properties:
> > +	- compatible: "parade,ps8640"
> > +	- reg: first i2c address of the bridge
> 
> Ther can be multiple addresses?

It means that the reg is the first page address of the continuous pages.

> 
> > +	- power-gpios: OF device-tree gpio specification for power pin.
> > +	- reset-gpios: OF device-tree gpio specification for reset pin.
> > +	- mode-sel-gpios: OF device-tree gpio specification for mode-sel
pin.
> > +	- ps8640-1v2-supply: OF device-tree regulator specification for
1v2.
> > +	- ps8640-3v3-supply: OF device-tree regulator specification for
3v3.
> 
> There's no need for the "ps8640-" prefix on these two. Please drop it.

OK, we will fix it in next patch.

> 
> > +Optional properties:
> > +	- video interfaces: Device node can contain video interface port
> > +			    nodes for panel according to [1].
> 
> Replace this part with:
> 
> The device node can contain video interface port nodes per the
> video-interfaces binding [1].

OK, we will fix it in next patch.

> 
> Thanks,
> Mark.
> 
> > +
> > +[1]: Documentation/devicetree/bindings/media/video-interfaces.txt
> > +
> > +Example:
> > +	edp-bridge@18 {
> > +		compatible = "parade,ps8640";
> > +		reg = <0x18>;
> > +		power-gpios = <&pio 116 GPIO_ACTIVE_HIGH>;
> > +		reset-gpios = <&pio 115 GPIO_ACTIVE_HIGH>;
> > +		mode-sel-gpios = <&pio 92 GPIO_ACTIVE_HIGH>;
> > +		ps8640-1v2-supply = <&ps8640_fixed_1v2>;
> > +		ps8640-3v3-supply = <&mt6397_vgp2_reg>;
> > +
> > +		ports {
> > +			#address-cells = <1>;
> > +			#size-cells = <0>;
> > +
> > +			port@0 {
> > +				reg = <0>;
> > +
> > +				ps8640_in: endpoint {
> > +					remote-endpoint = <&dsi0_out>;
> > +				};
> > +			};
> > +
> > +			port@1 {
> > +				reg = <1>;
> > +
> > +				ps8640_out: endpoint {
> > +					remote-endpoint = <&panel_in>;
> > +				};
> > +			};
> > +		};
> > +	};
> > --
> > 1.7.9.5
> >

             reply	other threads:[~2015-10-20  6:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  6:12 CK Hu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-20  7:22 [RFC 1/2] Dcumentation: bridge: Add documentation for ps8640 DT properties CK Hu
2015-10-20  7:02 CK Hu
2015-10-16 12:15 CK Hu
2015-10-16 13:04 ` Mark Rutland
2015-10-16 13:08 ` Philipp Zabel
     [not found] ` <1444997709-57293-1-git-send-email-ck.hu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-10-16 13:21   ` Rob Herring

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=1445321536.19417.5.camel@mtksdaap41 \
    --to=ck.hu@mediatek.com \
    --cc=airlied@linux.ie \
    --cc=ajaykumar.rs@samsung.com \
    --cc=andy.yan@rock-chips.com \
    --cc=cawa.cheng@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eddie.huang@mediatek.com \
    --cc=galak@codeaurora.org \
    --cc=inki.dae@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=srv_heupstream@mediatek.com \
    --cc=treding@nvidia.com \
    --cc=vpalatin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).