lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <8988677.GHLC4rSfsM@phil> Date: Tue, 24 May 2016 20:23:48 +0200 From: Heiko Stuebner <heiko@...ech.de> To: Doug Anderson <dianders@...omium.org> Cc: Yakir Yang <ykk@...k-chips.com>, David Airlie <airlied@...ux.ie>, Inki Dae <inki.dae@...sung.com>, Mark Yao <yzq@...k-chips.com>, Thierry Reding <treding@...dia.com>, Jingoo Han <jingoohan1@...il.com>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <k.kozlowski@...sung.com>, Daniel Vetter <daniel.vetter@...ll.ch>, Javier Martinez Canillas <javier@....samsung.com>, Emil Velikov <emil.l.velikov@...il.com>, Dan Carpenter <dan.carpenter@...cle.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>, linux-samsung-soc <linux-samsung-soc@...r.kernel.org>, "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org> Subject: Re: [PATCH v2 05/10] drm/rockchip: analogix_dp: add rk3399 eDP support Am Dienstag, 24. Mai 2016, 11:12:20 schrieb Doug Anderson: > Hi, > > On Tue, May 24, 2016 at 3:17 AM, Heiko Stuebner <heiko@...ech.de> 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).
Powered by blists - more mailing lists