Hello Jean, On Fri, Jan 08, 2010 at 01:52:22PM +0100, Jean Delvare wrote: > 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 Yes, I studied them yesterday in detail :) . The docs in i2c are also useful to get the big picture, thank you. That said, I'm currently stuck how to make the infrastructure probe ds2482. > 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. Yes, this is clear from your docs. > 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 As I wrote yesterday, I did try Method 4. However, /sys/bus/i2c/devices/i2c-0 doesn't exist. There is also ds2482_detect in ds2482.c of 2.6.27.25 (Method 3); still cannot see /sys/devices/w1_bus_master1. What is the problem there? Should I update some infrastructure files from 2.6 git? For now, I can't use newer kernels since they either hang or run very slowly ("time id" taking real 32s) on my board. > 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? I would gladly contribute that as soon as I learn how to do that :) . Thanks in advance, Baurzhan. -- 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
