diff options
author | Ingo Molnar <mingo@elte.hu> | 2008-07-17 19:24:56 +0200 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-07-17 19:24:56 +0200 |
commit | c43c1be0f7e0ac3d2fe1d4a5b37041c4c4463af1 (patch) | |
tree | 618b5e8ac458258acc981e0aeeac6f232f14aaf8 /Documentation/i2c/chips/pcf8575 | |
parent | e22146e610bb7aed63282148740ab1d1b91e1d90 (diff) | |
parent | a3cf859321486f69506326146ab3e2fd15c05c3f (diff) | |
download | op-kernel-dev-c43c1be0f7e0ac3d2fe1d4a5b37041c4c4463af1.zip op-kernel-dev-c43c1be0f7e0ac3d2fe1d4a5b37041c4c4463af1.tar.gz |
Merge branch 'linus' into x86/urgent
Diffstat (limited to 'Documentation/i2c/chips/pcf8575')
-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 25f5698..40b268e 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 -------------- |