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 89e69ad3436c6f62443335762797442605b1af1d..0d8be1c20c16b6bf96a95f42e7855d635e3a32b8 100644 (file)
--- a/Documentation/i2c/i2c-stub
+++ b/Documentation/i2c/i2c-stub
@@ -25,6 +25,9 @@ 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:
 
 int chip_addr[10]:
 PARAMETERS:
 
 int chip_addr[10]:


@@ -32,9 +35,6 @@ int chip_addr[10]:
 
 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.