On Fri, 8 Jan 2010 13:17:23 +0100, Baurzhan Ismagulov wrote: > Hello Jochen, > > On Fri, Jan 08, 2010 at 12:25:59PM +0100, Jochen Friedrich wrote: > >> There are boot messages about both. Creating /dev/i2c-0 and reading from > >> it result in appropriate debug messages. However, > >> /sys/devices/w1_bus_master1 is not created; the path described in > >> http://marc.info/?l=linux-i2c&m=125365009130579&w=2 does not exist. What > >> is the fastest way to get the application running on 2.6.27.25? > > > > What does your dts look like? Is the ds2482 present in the dts? > > Oh, that's an interesting point. No, it isn't present, only i2c. How did > it work in 2.6.25.7? I'd also appreciate pointers about that, if there > are any. You probably want to take a look at these 2 patches of mine which were applied to the ds2482 driver: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=61c91f7ded640bb2b340cc89d9ca3a3ca0229c74 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0314b020c49c1d6cd182d2b89775bfa6686660db The first one went in 2.6.27, the second in 2.6.32. > Currently I'm trying to understand why the new i2c infrastructure > doesn't call ds2482_probe, which creates the w1_bus_master1 directory. > Other ideas also welcome. Before 2.6.27, the ds2482 driver was a so-called "legacy i2c driver" probing buses randomly in search of supported chips. Since 2.6.27 is is a so-called "new-style i2c driver" which only attaches to the devices when told to. So what you observe is the expected behavior. It is much safer that way. For an overview of how an I2C device can be declared, see: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/i2c/instantiating-devices One method not described in this document is listing the device in a dts. It should probably be added, unfortunately I don't know enough about this myself to do it. Any volunteer? -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
