[i2c] Adaptive adapter name?

Jean Delvare khali at linux-fr.org
Fri Nov 3 11:22:19 CET 2006


On Thu, 2 Nov 2006 10:02:50 +0100 (MET), Till Harbaum wrote:
> > Can you explain exactly what you do mean by "lm_sensors looses the
> > configuration"? Are you using bus statements in your configuration
> > file? Otherwise the bus name is essentially informative and the change
> > shouldn't canse any problem.
> If i unplug the device and replug it and then enter "sensors" the sensor 
> doesn't show up anymore. I have to restart the sensor daemon (by restarting
> /etc/init/lm_sensors) to make the sensor show up again.
> This may of course be completely unrelated to the adapter name ...

There is no such thing as a "sensor daemon" [1]. I
guess /etc/init/lm_sensors is simply cycling the i2c bus and hardware
monitoring modules. If this is needed, this suggests that one of the
drivers doesn't support hotplug (assuming you enabled hotplug support
in your kernel?), and indeed I doubt this has anything to do with the
adapter name. You could try hardcoding the adapter name to confirm this.

A simple test would be to not load any hardware monitoring driver, only
your i2c bus driver, and use i2cdetect (and the i2c-dev driver) to
probe the bus before and after unplugging/replugging it. If probing
fails the second time, it means your bus driver doesn't properly
support hotplug. I can't say more without seeing the actual code,

[1] Actually there is a daemon named sensord, but "sensors" doesn't
need it and this is unrelated to your problem.

Jean Delvare

More information about the i2c mailing list