Hi Jean, On Fri, Mar 18, 2011 at 03:57:58AM -0400, Jean Delvare wrote: > On Thu, 17 Mar 2011 21:20:48 -0700, Guenter Roeck wrote: > > Hi all, > > > > I confirmed that DS1721, DS1631, DS1631A, and DS1731 > > work with the existing ds1621 driver: > > > > DS1721 (2x): > > ds1621-i2c-5-48 > > Adapter: i2c-devantech-iss at bus 002 device 034 > > temp1: +23.5°C (low = +10.0°C, high = +70.0°C) > > > > ds1621-i2c-5-49 > > Adapter: i2c-devantech-iss at bus 002 device 034 > > temp1: +23.5°C (low = +10.0°C, high = +70.0°C) > > > > DS1631: > > ds1621-i2c-5-4a > > Adapter: i2c-devantech-iss at bus 002 device 034 > > temp1: +23.0°C (low = +10.0°C, high = +70.0°C) > > > > DS1631A: > > ds1621-i2c-5-4b > > Adapter: i2c-devantech-iss at bus 002 device 034 > > temp1: +23.0°C (low = +10.0°C, high = +70.0°C) > > > > DS1731: > > ds1621-i2c-5-4c > > Adapter: i2c-devantech-iss at bus 002 device 034 > > temp1: +23.5°C (low = +10.0°C, high = +70.0°C) > > > > Output from sensors-detect: > > > > Driver `ds1621': > > * Bus `i2c-devantech-iss at bus 002 device 034' > > Busdriver `i2c_devantech_iss', I2C address 0x48 > > Chip `Dallas Semiconductor DS1621/DS1631' (confidence: 3) > > * Bus `i2c-devantech-iss at bus 002 device 034' > > Busdriver `i2c_devantech_iss', I2C address 0x49 > > Chip `Dallas Semiconductor DS1621/DS1631' (confidence: 3) > > * Bus `i2c-devantech-iss at bus 002 device 034' > > Busdriver `i2c_devantech_iss', I2C address 0x4a > > Chip `Dallas Semiconductor DS1621/DS1631' (confidence: 3) > > * Bus `i2c-devantech-iss at bus 002 device 034' > > Busdriver `i2c_devantech_iss', I2C address 0x4b > > Chip `Dallas Semiconductor DS1621/DS1631' (confidence: 3) > > * Bus `i2c-devantech-iss at bus 002 device 034' > > Busdriver `i2c_devantech_iss', I2C address 0x4c > > Chip `Dallas Semiconductor DS1621/DS1631' (confidence: 3) > > > > The chips still support register 0xee, even though that is not documented > > in the datasheets. > > > > Auto-detection and sensors-detect may or may not work depending > > on chip configuration (it always works after power-up). > > Explicit device instantiation always works. > > > > I'll update the list of supported devices to reflect this information. > > If memory serves, at least the DS1631 supports better resolution than > the ds1621 driver currently offers. So claiming that it is supported > isn't completely exact. What the driver supports is really the DS1621 > and the other chips happen to emulate it. > > It should really not be difficult to add proper support for all chips, > I just could never find the time to look into it. The chips I have here > are: one DS1621, two DS1631+ and two DS1624+. > Sure, can do that. What would you suggest ? Pick the best available resolution ? Also, if we do that, I would use i2c_device_id to select the part, and not try to auto-detect it. Another option would be to play with the configuration register and try detecting chip types this way (ie set bit 3,4 and observe the result). Not sure if that is a good idea, though. Any thoughts on this ? Thanks, Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
