i2c-piix4: Add AMD SB900 SMBus device ID

[mv-sheeva.git] / Documentation / i2c / i2c-stub

diff --git a/Documentation/i2c/i2c-stub b/Documentation/i2c/i2c-stub
index 9cc081e697648ecb3feaadddcc4b8da187294db9..0d8be1c20c16b6bf96a95f42e7855d635e3a32b8 100644 (file)
--- a/Documentation/i2c/i2c-stub
+++ b/Documentation/i2c/i2c-stub
@@ -6,13 +6,14 @@ This module is a very simple fake I2C/SMBus driver.  It implements four
 types of SMBus commands: write quick, (r/w) byte, (r/w) byte data, and
 (r/w) word data.
 
 types of SMBus commands: write quick, (r/w) byte, (r/w) byte data, and
 (r/w) word data.
 

-You need to provide a chip address as a module parameter when loading
-this driver, which will then only react to SMBus commands to this address.
+You need to provide chip addresses as a module parameter when loading this
+driver, which will then only react to SMBus commands to these addresses.

 
 No hardware is needed nor associated with this module.  It will accept write
 
 No hardware is needed nor associated with this module.  It will accept write

-quick commands to one address; it will respond to the other commands (also
-to one address) by reading from or writing to an array in memory.  It will
-also spam the kernel logs for every command it handles.
+quick commands to the specified addresses; it will respond to the other
+commands (also to the specified addresses) by reading from or writing to
+arrays in memory.  It will also spam the kernel logs for every command it
+handles.

 
 A pointer register with auto-increment is implemented for all byte
 operations.  This allows for continuous byte reads like those supported by
 
 A pointer register with auto-increment is implemented for all byte
 operations.  This allows for continuous byte reads like those supported by


@@ -24,16 +25,16 @@ The typical use-case is like this:
        3. load the target sensors chip driver module
        4. observe its behavior in the kernel log
 
        3. load the target sensors chip driver module
        4. observe its behavior in the kernel log
 

+There's a script named i2c-stub-from-dump in the i2c-tools package which
+can load register values automatically from a chip dump.
+

 PARAMETERS:
 
 PARAMETERS:
 

-int chip_addr:
-       The SMBus address to emulate a chip at.
+int chip_addr[10]:
+       The SMBus addresses to emulate chips at.

 
 CAVEATS:
 
 
 CAVEATS:
 

-There are independent arrays for byte/data and word/data commands.  Depending
-on if/how a target driver mixes them, you'll need to be careful.
-

 If your target driver polls some byte or word waiting for it to change, the
 stub could lock it up.  Use i2cset to unlock it.
 
 If your target driver polls some byte or word waiting for it to change, the
 stub could lock it up.  Use i2cset to unlock it.
 


@@ -41,9 +42,6 @@ If the hardware for your driver has banked registers (e.g. Winbond sensors
 chips) this module will not work well - although it could be extended to
 support that pretty easily.
 
 chips) this module will not work well - although it could be extended to
 support that pretty easily.
 

-Only one chip address is supported - although this module could be
-extended to support more.
-

 If you spam it hard enough, printk can be lossy.  This module really wants
 something like relayfs.
 
 If you spam it hard enough, printk can be lossy.  This module really wants
 something like relayfs.