[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1243496925.3171.151.camel@pasglop>
Date: Thu, 28 May 2009 17:48:45 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Robert Schwebel <r.schwebel@...gutronix.de>
Cc: Grant Likely <grant.likely@...retlab.ca>,
devicetree-discuss <devicetree-discuss@...abs.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Janboe Ye <yuan-bo.ye@...orola.com>,
linux-kernel@...r.kernel.org, Timur Tabi <timur@...escale.com>,
Jon Smirl <jonsmirl@...il.com>,
Scott Wood <scottwood@...escale.com>,
linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform
On Thu, 2009-05-28 at 01:57 +0200, Robert Schwebel wrote:
> On Wed, May 27, 2009 at 02:22:50PM -0600, Grant Likely wrote:
> > 2) Driver binding mechanism: device tree nodes usually have a
> > "compatible" property which is a list of strings. The first string
> > describes exactly what the device is (ie. "atmel,24c08") and an
> > optional list of other devices which it is register interface
> > backwards compatible with.
>
> This is a good example. The "exact" description above doesn't say
> anything about some of the details the driver needs to know. Here is the
> at24 driver:
>
> http://lxr.linux.no/linux+v2.6.29/include/linux/i2c/at24.h#L18
>
> Where do we get the page size & flags from?
Easy, add properties for them in the node for that device ! The
device-tree actually makes that really easy, a lot easier than anything
else I've seen so far.
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/
Powered by blists - more mailing lists