Hi, Thank you so much for help.
> yes, if you have the proper struct i2c_driver and struct i2c_device_id in > your driver the i2c subsystem should call the probe of your device. > > check drivers/i2c/chips/menelaus.c for an example. > > See how I2C_BOARD_INFO() in arch/arm/mach-omap2/board-h4 > and struct i2c_device_id have the same name for the device (menelaus). I am not using the last snapshot of Linux, but the 2.6.23 release. My source code is not completly up-to-date. For example there is no reference of I2C_BOARD_INFO in board-h4. I have no 'i2c_device_id menelaus_id[]' in the i2c drivers code. Perhap's that's why I am quite confuse, I am refering to recent code examples and I am using not-so-recent Linux version. In the documentation, "New-style" drivers are presented very quickly. In fact, I still don't know where must be located the valid client list: - in the board init source code with I2C_BOARD_INFO() macro - in the i2c driver source code > no, i2c layer will call device probe based on the driver name being the same > in > i2c_board_info and i2c_device_id (if I'm not wrong that's the match, > Jean correct > me if I'm wrong). > With my Linux version, i2c_device_id list was not present in the i2c_driver structure. So i2c_board_info is supposed to match with what ? > That's old style i2c driver. You don't need that anymore ;-) Cool :) Lines removed ! Best regards, Légion. _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
