linux-kernel - Re: [RFC] [PATCH] Device Tree on ARM platform

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: <1243496321.3171.141.camel@pasglop>
Date:	Thu, 28 May 2009 17:38:41 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Scott Wood <scottwood@...escale.com>
Cc:	Russell King <rmk+lkml@....linux.org.uk>,
	devicetree-discuss <devicetree-discuss@...abs.org>,
	linux-kernel@...r.kernel.org, Timur Tabi <timur@...escale.com>,
	Janboe Ye <yuan-bo.ye@...orola.com>,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform

On Wed, 2009-05-27 at 14:08 -0500, Scott Wood wrote:
> But to restate, having external glue to create platform devices from the 
> device tree is fine if that's what you want to do.  We used to do that, 
> but it was a pain compared to keeping everything in one place.  Your 
> experience may differ.

This is a non-solved debate as to what is best. If an existing driver
already has fairly complete platform_device support, it might be best to
just create a glue that fills up the data structure from the DT... 

In any case, all the approaches are possible, the DT stuff doesn't
corner you into a specific one.

Cheers,
Ben.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/