Re: [RFC] [PATCH] Device Tree on ARM platform
From: Grant Likely
Date: Thu May 28 2009 - 10:47:42 EST
On Thu, May 28, 2009 at 8:17 AM, Ben Dooks <ben-linux@xxxxxxxxx> wrote:
> On Wed, May 27, 2009 at 03:13:55PM -0400, Jon Smirl wrote:
>> On Wed, May 27, 2009 at 3:08 PM, Scott Wood <scottwood@xxxxxxxxxxxxx> wrote:
>> > I'm not talking about platform specific code, I'm talking about code to
>> > retrieve information about a device from the device tree. There would not
>> > be separate instances of this for "platforms X, Y and Z", just one
>> > of_platform binding in each driver. It's no different than having a
>> > platform bus binding, except in the data structures used.
>> > 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.
>> Could 'struct platform_device' and 'struct of_platform_device" be
>> unified into a single structure? It's personal preference whether the
>> internal representation of the hardware is done via a device tree or
>> snippets of platform code, but do we need to have to different device
> I was wondering what the pros/cons of having a system that takes a
> device tree and manufactures platform devices / etc from it? I think
> one of the cons is that if you change the platform device data, then
> you have not only the board definitions to change, but the of->platform
> code to modify as well...
Yes, this is the long term goal. And not just platform devices
either, i2c, spi, mdio, etc. The current problem is that there still
needs to be a per-driver mechanism to translate device tree data into
the correct pdata structure. That code is not hard, but it is
undetermined what is best for where that code should live and how it
should be triggered.
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/