| commit | 0d73adc14e239b05a9393c09c067a26a5ba86b6c | |
| author | Jean Delvare <khali@linux-fr.org> | |
| Fri, 29 Jul 2005 19:15:33 +0000 (29 12:15 -0700) | ||
| committer | Linus Torvalds <torvalds@g5.osdl.org> | |
| Fri, 29 Jul 2005 20:12:51 +0000 (29 13:12 -0700) | ||
| tree | 2d37b52c21c02c4f7be2e2551abad3d4cbc69e73 | treesnapshot (tar.gz zip) |
| parent | 86749e8512d2c37618dc5814ef41abbf168f291b | commitdiff |
[PATCH] I2C: 24RF08 corruption prevention (again)
The 24RF08 corruption prevention in the eeprom and max6875 drivers wasn't
complete. For one thing, the additional quick write should happen as soon
as possible and unconditionally, while both drivers had error paths before.
For another, when a given chip is forced, the core does not emit a quick
write, so a second quick write would cause the corruption rather than
prevent it.
I plan to move the corruption prevention in the core in the long run, so
that individual drivers don't have to care anymore. But I need to merge
i2c_probe and i2c_detect before I do (work in progress).
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
The 24RF08 corruption prevention in the eeprom and max6875 drivers wasn't
complete. For one thing, the additional quick write should happen as soon
as possible and unconditionally, while both drivers had error paths before.
For another, when a given chip is forced, the core does not emit a quick
write, so a second quick write would cause the corruption rather than
prevent it.
I plan to move the corruption prevention in the core in the long run, so
that individual drivers don't have to care anymore. But I need to merge
i2c_probe and i2c_detect before I do (work in progress).
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| drivers/i2c/chips/eeprom.c | diffblobblamehistory | |
| drivers/i2c/chips/max6875.c | diffblobblamehistory |