On Thu, Apr 16, 2009 at 03:36:12PM +0200, Michael Lawnick wrote:
> Wolfram Sang said the following:
> >> Could you please elaborate?
> >
> > Instead of probing you specify the devices on the i2c-bus in the dts. Example
> > for the pcm032 looks like this (from the kernel-tree):
> >
> > i2c@3d40 {
> > #address-cells = <1>;
> > #size-cells = <0>;
> > compatible = "fsl,mpc5200b-i2c","fsl,mpc5200-i2c","fsl-i2c";
> > reg = <0x3d40 0x40>;
> > interrupts = <2 16 0>;
> > fsl5200-clocking;
> >
> > rtc@51 {
> > compatible = "nxp,pcf8563";
> > reg = <0x51>;
> > };
> > eeprom@52 {
> > compatible = "at24,24c32";
> > reg = <0x52>;
> > };
> > };
> >
> > Boards which relied on probing need to have such child nodes added.
>
> Ok, that doesn't help :-(
> I hoped you show me a way how to set the class of adapter. My clients
> are loaded with insmod, so dts has no effect (or is this wrong?)
Are you sure you put the correct names into the compatible field?
With my dts-files, I can see the i2c-devices in sysfs. After modprobing
the necessary modules, I can access the devices. Example on my current
board:
root@A:~ hwclock -r
hwclock: can't open '/dev/misc/rtc': No such file or directory
root@A:~ modprobe rtc-ds1307
rtc-ds1307 0-0068: rtc core: registered ds3231 as rtc0
root@A:~ hwclock -r
Sat Jan 1 01:23:06 2000 0.000000 seconds
root@A:~ hwclock -r
Sat Jan 1 01:23:12 2000 0.000000 seconds
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Attachment:
signature.asc
Description: Digital signature
