From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755432AbcEXSYU (ORCPT ); Tue, 24 May 2016 14:24:20 -0400 Received: from gloria.sntech.de ([95.129.55.99]:51892 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752184AbcEXSYT (ORCPT ); Tue, 24 May 2016 14:24:19 -0400 From: Heiko Stuebner To: Doug Anderson Cc: Yakir Yang , David Airlie , Inki Dae , Mark Yao , Thierry Reding , Jingoo Han , Rob Herring , Krzysztof Kozlowski , Daniel Vetter , Javier Martinez Canillas , Emil Velikov , Dan Carpenter , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , linux-samsung-soc , "open list:ARM/Rockchip SoC..." Subject: Re: [PATCH v2 05/10] drm/rockchip: analogix_dp: add rk3399 eDP support Date: Tue, 24 May 2016 20:23:48 +0200 Message-ID: <8988677.GHLC4rSfsM@phil> User-Agent: KMail/4.14.10 (Linux/4.3.0-1-amd64; KDE/4.14.14; x86_64; ; ) In-Reply-To: References: <1464066147-22734-1-git-send-email-ykk@rock-chips.com> <6183955.XzKjc41sjW@phil> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Dienstag, 24. Mai 2016, 11:12:20 schrieb Doug Anderson: > Hi, > > On Tue, May 24, 2016 at 3:17 AM, Heiko Stuebner wrote: > >> --- a/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt > >> +++ b/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt > >> > >> @@ -5,6 +5,7 @@ Required properties for dp-controller: > >> platform specific such as: > >> * "samsung,exynos5-dp" > >> * "rockchip,rk3288-dp" > >> > >> + * "rockchip,rk3399-edp" > > > > the cleanlines-freak in my likes to know if there is a difference > > between > > the rk3399 being called -edp here and -dp on the rk3288 :-) > > > > [...] > > If I was a guessing man (which I'm not, but if I was), I'd guess that > this is because on rk3288 there was only one DP port and it was an EDP > port. ...but since there was only one people just referred to it as > the "DP" port and that was codified in the bindings. On rk3399 there > are two ports: one EDP and one DP. All of a sudden we need to > differentiate. > > Any better suggestions for how to deal with that? nope - everything as it should be in that regard then - the rk3288-dp is permanent now anyway. But it looks like I'm sort of blind blind and only now have seen the separate DP controller chapter in the TRM (probably because I somehow didn't expect a second controller).