diff options
| author | Jean Delvare <khali@linux-fr.org> | 2008-07-16 19:30:06 +0200 |
|---|---|---|
| committer | Jean Delvare <khali@mahadeva.delvare> | 2008-07-16 19:30:06 +0200 |
| commit | 97addff6def3f8e228a634fa017589f45c69de5c (patch) | |
| tree | abdbe65bb56dd88dbdaeb1878168ef4640ff829c /Documentation/i2c | |
| parent | 833bedb813689807385ae73175389c73a3f855c1 (diff) | |
| download | kernel-crypto-97addff6def3f8e228a634fa017589f45c69de5c.tar.gz kernel-crypto-97addff6def3f8e228a634fa017589f45c69de5c.tar.xz kernel-crypto-97addff6def3f8e228a634fa017589f45c69de5c.zip | |
i2c: Convert the pcf8575 driver to a new-style i2c driver
The new-style pcf8575 driver implements the optional detect() callback
to cover the use cases of the legacy driver.
Warning: users will now have to use the force module parameter to get
the driver to attach to their device. That's not a bad thing as these
devices can't be detected anyway.
Note that this doesn't change the fact that this driver is deprecated
in favor of gpio/pcf857x.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'Documentation/i2c')
| -rw-r--r-- | Documentation/i2c/chips/pcf8575 | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/Documentation/i2c/chips/pcf8575 b/Documentation/i2c/chips/pcf8575 index 25f5698a61c..40b268eb276 100644 --- a/Documentation/i2c/chips/pcf8575 +++ b/Documentation/i2c/chips/pcf8575 @@ -40,12 +40,9 @@ Detection --------- There is no method known to detect whether a chip on a given I2C address is -a PCF8575 or whether it is any other I2C device. So there are two alternatives -to let the driver find the installed PCF8575 devices: -- Load this driver after any other I2C driver for I2C devices with addresses - in the range 0x20 .. 0x27. -- Pass the I2C bus and address of the installed PCF8575 devices explicitly to - the driver at load time via the probe=... or force=... parameters. +a PCF8575 or whether it is any other I2C device, so you have to pass the I2C +bus and address of the installed PCF8575 devices explicitly to the driver at +load time via the force=... parameter. /sys interface -------------- |