Received: by 10.213.65.68 with SMTP id h4csp381518imn; Tue, 27 Mar 2018 00:34:56 -0700 (PDT) X-Google-Smtp-Source: AG47ELsqJWDqU8zeRo9HekZiJ0isJoCMHV1tuWAw3VdrDPACB+fnYYESurRH8BJSEaX1nTOBdPFT X-Received: by 10.99.47.4 with SMTP id v4mr21482530pgv.42.1522136096439; Tue, 27 Mar 2018 00:34:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522136096; cv=none; d=google.com; s=arc-20160816; b=HBMYnDYw6eGvaGp7KSxK1ZvE4C3F3IhOIopr9+k787sn312P/xT/7CMZQRGmgfDWYt IowhVA9e/93r4smSExjKVYDnbRck8NOQf6ZQ4kWg4wSxy9I5tp9K+YWA6G8AP8q2VgTk FBiS380s/am2u6kRfm03kDRUSruZOxIlw5AnOcQwjp20myK/YN1ZNnqyncSDUCJ/lZKh ikxrxTtT3+snMEHW92dQNi6XPA22CaJw4fcXnw3LzVMJs4nOoovS2vG/vajEaXNEuRUG BjKOjmXDTb23p2MGpGVtL2DSH8JqpGmy1zC9dNGMcyC18iWp8+u00C4QRLkR6o9UKMdR u24A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=VPKkaPIErbm/8X0qjilgjmbeqwLdw8AMHsEHn78gNss=; b=Wd6565KeDYdzgatDWOZnATk3sZYpfOwY/4Z8rz4lNDPTBrmyjuR9BT4VETHRcBwzqi ZMNl6S2WL4EHwygkipI5sUJts6jAHrkJNYgBMrGv7S/S0jQ/Bx3Iocf6CYI2nWktVkeT E8YgNHSj2ukzmpjPqN2tjSlr4IstAaIj/xGkYWB/RFx5yKgLUC0ziCSIWO7QloLMHrQb Re8l90NmwXSr/Lvsg9MWcHE5LH2nEYcO4Pl0Xya2orA/IBBQgCsLuBer+REC2OwNA8vh VYeWuqNvoGo8vfPJoRn/U31LTzDT4O5Q6yYUbdOgspyif2jh0pWLlmPhCCYZFq0V+u4G LuQg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i1si434455pgv.519.2018.03.27.00.34.42; Tue, 27 Mar 2018 00:34:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751859AbeC0Hdm (ORCPT + 99 others); Tue, 27 Mar 2018 03:33:42 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:54747 "EHLO relay9-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750932AbeC0Hdk (ORCPT ); Tue, 27 Mar 2018 03:33:40 -0400 X-Originating-IP: 2.224.242.101 Received: from w540 (unknown [2.224.242.101]) (Authenticated sender: jacopo@jmondi.org) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 78E70FF811; Tue, 27 Mar 2018 09:33:34 +0200 (CEST) Date: Tue, 27 Mar 2018 09:33:32 +0200 From: jacopo mondi To: Andrzej Hajda Cc: Vladimir Zapolskiy , Jacopo Mondi , Rob Herring , Laurent Pinchart , 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 Message-ID: <20180327073332.GI27746@w540> References: <1521213399-31947-1-git-send-email-jacopo+renesas@jmondi.org> <1521213399-31947-2-git-send-email-jacopo+renesas@jmondi.org> <4060923.7DxT9ae38L@avalon> <20180326222249.tvjiutyd4amlibpa@rob-hp-laptop> <1dd27170-153c-90f6-e13f-949ba7d0d4a9@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1dd27170-153c-90f6-e13f-949ba7d0d4a9@samsung.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andrzej, On Tue, Mar 27, 2018 at 09:12:46AM +0200, Andrzej Hajda wrote: > 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 > >>>> Reviewed-by: Andrzej Hajda > >>>> Reviewed-by: Niklas Söderlund > >>>> --- > >>>> .../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 > >>> > >>>> +- 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? Seconded. My understanding is that the property name should reflect what reported in the the chip manual. For THC63LVD1024 the enable and power down pins are named 'OE' and 'PDWN' respectively. Thanks j > > 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 > > > > > > >