From: Andrzej Hajda <a.hajda@samsung.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: Rob Herring <robh@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
architt@codeaurora.org, airlied@linux.ie, horms@verge.net.au,
magnus.damm@gmail.com, geert@linux-m68k.org,
niklas.soderlund@ragnatech.se,
sergei.shtylyov@cogentembedded.com, mark.rutland@arm.com,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder
Date: Tue, 27 Mar 2018 09:12:46 +0200 [thread overview]
Message-ID: <1dd27170-153c-90f6-e13f-949ba7d0d4a9@samsung.com> (raw)
In-Reply-To: <a1b0e678-38b8-dd29-b441-e2a09b565105@mentor.com>
On 27.03.2018 08:15, Vladimir Zapolskiy wrote:
> Hi Jacopo,
>
> On 03/27/2018 01:22 AM, Rob Herring wrote:
>> On Tue, Mar 20, 2018 at 02:43:33PM +0200, Laurent Pinchart wrote:
>>> Hi Jacopo,
>>>
>>> (CC'ing Rob)
>>>
>>> Thank you for the patch.
>>>
>>> On Friday, 16 March 2018 17:16:37 EET Jacopo Mondi wrote:
>>>> Document Thine THC63LVD1024 LVDS decoder device tree bindings.
>>>>
>>>> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
>>>> Reviewed-by: Andrzej Hajda <a.hajda@samsung.com>
>>>> Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>>>> ---
>>>> .../bindings/display/bridge/thine,thc63lvd1024.txt | 66 +++++++++++++++++++
>>>> 1 file changed, 66 insertions(+)
>>>> create mode 100644
>>>> Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
>>>>
>>>> diff --git
>>>> a/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
>>>> b/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
>>>> new file mode 100644
>>>> index 0000000..8225c6a
>>>> --- /dev/null
>>>> +++
>>>> b/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
>>>> @@ -0,0 +1,66 @@
>>>> +Thine Electronics THC63LVD1024 LVDS decoder
>>>> +-------------------------------------------
>>>> +
>>>> +The THC63LVD1024 is a dual link LVDS receiver designed to convert LVDS
>>>> streams
>>>> +to parallel data outputs. The chip supports single/dual input/output modes,
>>>> +handling up to two two input LVDS stream and up to two digital CMOS/TTL
>>>> outputs.
>>>> +
>>>> +Single or dual operation modes, output data mapping and DDR output modes
>>>> are
>>>> +configured through input signals and the chip does not expose any control
>>>> bus.
>>>> +
>>>> +Required properties:
>>>> +- compatible: Shall be "thine,thc63lvd1024"
>>>> +
>>>> +Optional properties:
>>>> +- vcc-supply: Power supply for TTL output and digital circuitry
>>>> +- cvcc-supply: Power supply for TTL CLOCKOUT signal
>>>> +- lvcc-supply: Power supply for LVDS inputs
>>>> +- pvcc-supply: Power supply for PLL circuitry
>>> As explained in a comment to one of the previous versions of this series, I'm
>>> tempted to make vcc-supply mandatory and drop the three other power supplies
>>> for now, as I believe there's very little chance they will be connected to
>>> separately controllable regulators (all supplies use the same voltage). In the
>>> very unlikely event that this occurs in design we need to support in the
>>> future, the cvcc, lvcc and pvcc supplies can be added later as optional
>>> without breaking backward compatibility.
>> I'm okay with that.
>>
>>> Apart from that,
>>>
>>> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>>
>>>> +- pdwn-gpios: Power down GPIO signal. Active low
>> powerdown-gpios is the semi-standard name.
>>
> right, I've also noticed it. If possible please avoid shortenings in
> property names.
It is not shortening, it just follow pin name from decoder's datasheet.
>
>>>> +- oe-gpios: Output enable GPIO signal. Active high
>>>> +
> And this one is also a not ever met property name, please consider to
> rename it to 'enable-gpios', for instance display panels define it.
Again, it follows datasheet naming scheme. Has something changed in DT
conventions?
Regards
Andrzej
>
>>>> +The THC63LVD1024 video port connections are modeled according
>>>> +to OF graph bindings specified by
>>>> Documentation/devicetree/bindings/graph.txt
> [snip]
>
>>>> +
>>>> + port@2{
>>>> + reg = <2>;
>>>> +
>>>> + lvds_dec_out_2: endpoint {
>>>> + remote-endpoint = <&adv7511_in>;
>>>> + };
>>>> +
> Drop a surplus empty line above.
>
>>>> + };
>>>> +
> Drop a surplus empty line above.
>
>>>> + };
>>>> + };
> --
> With best wishes,
> Vladimir
>
>
>
next prev parent reply other threads:[~2018-03-27 7:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 15:16 [PATCH v6 0/3] drm: Add Thine THC63LVD1024 LVDS decoder bridge Jacopo Mondi
2018-03-16 15:16 ` [PATCH v6 1/3] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder Jacopo Mondi
2018-03-20 12:43 ` Laurent Pinchart
2018-03-26 12:08 ` jacopo mondi
2018-03-26 22:22 ` Rob Herring
2018-03-27 6:15 ` Vladimir Zapolskiy
2018-03-27 7:12 ` Andrzej Hajda [this message]
2018-03-27 7:33 ` jacopo mondi
2018-03-27 8:27 ` Sergei Shtylyov
2018-03-27 8:30 ` Vladimir Zapolskiy
2018-03-27 8:57 ` jacopo mondi
2018-03-27 9:37 ` Vladimir Zapolskiy
2018-03-27 10:10 ` jacopo mondi
2018-03-27 11:03 ` Vladimir Zapolskiy
2018-03-29 10:02 ` jacopo mondi
2018-04-02 13:36 ` Laurent Pinchart
2018-04-03 12:33 ` jacopo mondi
2018-04-05 16:33 ` Rob Herring
2018-04-05 18:53 ` Laurent Pinchart
2018-04-05 21:27 ` Rob Herring
2018-03-16 15:16 ` [PATCH v6 2/3] drm: bridge: Add thc63lvd1024 LVDS decoder driver Jacopo Mondi
2018-03-20 13:00 ` Laurent Pinchart
2018-03-27 6:24 ` Vladimir Zapolskiy
2018-03-27 7:28 ` Andrzej Hajda
2018-03-27 7:36 ` Geert Uytterhoeven
2018-03-27 8:36 ` Andrzej Hajda
2018-03-27 9:06 ` Geert Uytterhoeven
2018-03-27 9:57 ` Vladimir Zapolskiy
2018-03-27 7:30 ` jacopo mondi
2018-03-16 15:16 ` [PATCH v6 3/3] arm64: dts: renesas: Add LVDS decoder to R-Car V3M Eagle Jacopo Mondi
2018-03-20 13:01 ` Laurent Pinchart
2018-03-27 6:27 ` Vladimir Zapolskiy
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=1dd27170-153c-90f6-e13f-949ba7d0d4a9@samsung.com \
--to=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=robh@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vladimir_zapolskiy@mentor.com \
/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
all inboxes | Powered by JetHome®