mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 19:21:31 -04:00
hwmon: (zl6100) Enable interval between chip accesses for all chips
Intersil reports that all chips supported by the zl6100 driver require an interval between chip accesses, even ZL2004 and ZL6105 which were thought to be safe. Reported-by: Vivek Gani <[email protected]> Cc: [email protected] # 3.2+ Signed-off-by: Guenter Roeck <[email protected]>
This commit is contained in:
parent
c43524b580
commit
fecfb64422
2 changed files with 9 additions and 17 deletions
|
|
@ -200,17 +200,11 @@ static int zl6100_probe(struct i2c_client *client,
|
|||
data->id = mid->driver_data;
|
||||
|
||||
/*
|
||||
* ZL2005, ZL2008, ZL2105, and ZL6100 are known to require a wait time
|
||||
* between I2C accesses. ZL2004 and ZL6105 are known to be safe.
|
||||
* Other chips have not yet been tested.
|
||||
*
|
||||
* Only clear the wait time for chips known to be safe. The wait time
|
||||
* can be cleared later for additional chips if tests show that it
|
||||
* is not needed (in other words, better be safe than sorry).
|
||||
* According to information from the chip vendor, all currently
|
||||
* supported chips are known to require a wait time between I2C
|
||||
* accesses.
|
||||
*/
|
||||
data->delay = delay;
|
||||
if (data->id == zl2004 || data->id == zl6105)
|
||||
data->delay = 0;
|
||||
|
||||
/*
|
||||
* Since there was a direct I2C device access above, wait before
|
||||
|
|
|
|||
Loading…
Reference in a new issue