linux-kernel - Re: [RFC PATCH 0/2] drm/panel: add simple-panel description using DT

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140513075148.GF6754@ulmo>
Date:	Tue, 13 May 2014 09:51:50 +0200
From:	Thierry Reding <thierry.reding@...il.com>
To:	Boris BREZILLON <boris.brezillon@...e-electrons.com>
Cc:	Randy Dunlap <rdunlap@...radead.org>,
	David Airlie <airlied@...ux.ie>,
	Jean-Jacques Hiblot <jjhiblot@...phandler.com>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] drm/panel: add simple-panel description using DT

On Fri, May 09, 2014 at 04:16:40PM +0200, Boris BREZILLON wrote:
> Hello Thierry,
> 
> I noticed you're describing each new panel with a new entry in the
> of_platform_match table and a new compatible string.
> I guess you have a good reason to do it this way, because retrieving
> panel description from DT would be pretty easy (see this series ;-)).
> 
> Could tell me why you chose this approach ?

The reason is that devicetree mandates that a device be identified using
a compatible value and that compatible value should be as specific as
possible. That compatible value should give the device driver enough
information to know everything it needs (resolution, timings, physical
dimension).

Having all of that data in the device tree is redundant.

Thierry

Content of type "application/pgp-signature" skipped