diff options
| author | Jean Delvare <khali@linux-fr.org> | 2008-05-18 20:49:41 +0200 |
|---|---|---|
| committer | Jean Delvare <khali@hyperion.delvare> | 2008-05-18 20:49:41 +0200 |
| commit | 70455e790391dac85d9b483a9e286a40df1ecc7f (patch) | |
| tree | f5ea301f7aaec341e718fb187d81d3afa65ec6bd | |
| parent | 875b0a473c3ddd80bc4ae88a65cd20027428e160 (diff) | |
| download | kernel_samsung_tuna-70455e790391dac85d9b483a9e286a40df1ecc7f.zip kernel_samsung_tuna-70455e790391dac85d9b483a9e286a40df1ecc7f.tar.gz kernel_samsung_tuna-70455e790391dac85d9b483a9e286a40df1ecc7f.tar.bz2 | |
i2c/max6875: Really prevent 24RF08 corruption
i2c-core takes care of the possible corruption of 24RF08 chips for
quite some times, so device devices no longer need to do it. And they
really should not, as applying the prevention twice voids it.
I thought that I had fixed all drivers long ago but apparently I had
missed that one.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Ben Gardner <bgardner@wabtec.com>
| -rw-r--r-- | drivers/i2c/chips/max6875.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/i2c/chips/max6875.c b/drivers/i2c/chips/max6875.c index fb7ea56..cf507b3 100644 --- a/drivers/i2c/chips/max6875.c +++ b/drivers/i2c/chips/max6875.c @@ -207,9 +207,6 @@ static int max6875_detect(struct i2c_adapter *adapter, int address, int kind) fake_client->flags = 0; strlcpy(fake_client->name, "max6875 subclient", I2C_NAME_SIZE); - /* Prevent 24RF08 corruption (in case of user error) */ - i2c_smbus_write_quick(real_client, 0); - if ((err = i2c_attach_client(real_client)) != 0) goto exit_kfree2; |