Re: Q: define i2c nodes in device tree?

On Fri, Mar 27, 2009 at 8:05 AM, Albrecht Dre=DF [off-list ref] =
wrote:

Now the driver is called, but complains that no platform data is present.=

 =A0Still have to figure out how to pass that... :-/

I believe there was code added recently to i2c-mpc.c to put DTS
properties into the platform device, but I don't see it right now.

# ls -al /sys/devices/f0000000.soc5200/f0003d40.i2c/i2c-adapter/i2c-1/
drwxr-xr-x =A0 =A06 0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 Jan =

=A01 00:00 .

drwxr-xr-x =A0 =A03 0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 Jan =

=A01 00:00 ..

drwxr-xr-x =A0 =A02 0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 Jan =

=A01 00:00 1-0020

drwxr-xr-x =A0 =A02 0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 Jan =

=A01 00:00 1-0021

drwxr-xr-x =A0 =A02 0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 Jan =

=A01 00:00 1-0022

[...]

Is this the intended behaviour?

I think the entries in /sys/devices/f0000000.soc5200 are from the
device tree directly.  They're not related to any device driver.  I
believe you'll find those entries still there even if your driver
isn't loaded at all.

--=20
Timur Tabi
Linux kernel developer at Freescale