diff options
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 25f5698a61cf..40b268eb276f 100644 --- a/Documentation/i2c/chips/pcf8575 +++ b/Documentation/i2c/chips/pcf8575 | |||
| @@ -40,12 +40,9 @@ Detection | |||
| 40 | --------- | 40 | --------- |
| 41 | 41 | ||
| 42 | There is no method known to detect whether a chip on a given I2C address is | 42 | There is no method known to detect whether a chip on a given I2C address is |
| 43 | a PCF8575 or whether it is any other I2C device. So there are two alternatives | 43 | a PCF8575 or whether it is any other I2C device, so you have to pass the I2C |
| 44 | to let the driver find the installed PCF8575 devices: | 44 | bus and address of the installed PCF8575 devices explicitly to the driver at |
| 45 | - Load this driver after any other I2C driver for I2C devices with addresses | 45 | load time via the force=... parameter. |
| 46 | in the range 0x20 .. 0x27. | ||
| 47 | - Pass the I2C bus and address of the installed PCF8575 devices explicitly to | ||
| 48 | the driver at load time via the probe=... or force=... parameters. | ||
| 49 | 46 | ||
| 50 | /sys interface | 47 | /sys interface |
| 51 | -------------- | 48 | -------------- |