From: CK Hu <ck.hu@mediatek.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
"; Pawel Moll" <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"; Kumar Gala" <galak@codeaurora.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"; Jitao Shi" <jitao.shi@mediatek.com>,
Thierry, Ajay, Inki, Rahul Sharma <rahul.sharma@samsung.com>,
"; Sean Paul" <seanpaul@chromium.org>,
Andy Yan <andy.yan@rock-chips.com>,
"; Russell King" <rmk+kernel@arm.linux.org.uk>,
"; 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 Chen <yingjoe.chen@mediatek.com>,
; 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 15:02:44 +0800 [thread overview]
Message-ID: <1445324564.19417.13.camel@mtksdaap41> (raw)
Hi, Philipp:
> -----Original Message-----
> From: Philipp Zabel [mailto:p.zabel@pengutronix.de]
> Sent: Friday, October 16, 2015 9:09 PM
> Subject: Re: [RFC 1/2] Dcumentation: bridge: Add documentation for
ps8640
> DT properties
>
> Hi CK,
>
> there is a typo in the subject: s/Dcumentation/Documentation/.
We will correct next patch.
>
> Am Freitag, den 16.10.2015, 20:15 +0800 schrieb CK Hu:
> > From: Jitao Shi <jitao.shi@mediatek.com>
> >
> > Add documentation for DT properties supported by ps8640 DSI-eDP
> > converter.
> >
> > Signed-off-by: Jitao Shi <jitao.shi@mediatek.com>
> [...]
> > + - ps8640-1v2-supply: OF device-tree regulator specification for
1v2.
> > + - ps8640-3v3-supply: OF device-tree regulator specification for
3v3.
>
> The ps8640- part of the regulator supply property names is redundant.
> The PS8622 driver uses vdd12-supply as its regulator. Should we strive
for
> consistency here? Or if you have access to the datasheet, how are
these inputs
> called there?
yes, we should use vdd12-supply and vdd33-supply, we'll fixed it in next
patch.
>
> > +
> > +Optional properties:
> > + - video interfaces: Device node can contain video interface port
> > + nodes for panel according to [1].
> > +
> > +[1]: Documentation/devicetree/bindings/media/video-interfaces.txt
>
> It should be documented here that port@0 is the input port and port@1
is the
> output port.
Yes, port@0 is the input port and port@1 is the output port. We'll add
the info in next patch.
>
> best regards
> Philipp
next reply other threads:[~2015-10-20 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 7:02 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 6:12 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=1445324564.19417.13.camel@mtksdaap41 \
--to=ck.hu@mediatek.com \
--cc=andy.yan@rock-chips.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jitao.shi@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=rahul.sharma@samsung.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=seanpaul@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).