aboutsummaryrefslogtreecommitdiff
path: root/Documentation/i2c/i2c-stub
diff options
context:
space:
mode:
authorJean Delvare <khali@linux-fr.org>2008-01-27 18:14:45 +0100
committerJean Delvare <khali@hyperion.delvare>2008-01-27 18:14:45 +0100
commitb3af547e197fa3ca648d148dd8d36befe989e5a0 (patch)
tree68c51d5af0f6eaac3062d40f88af69f2c4d91f5e /Documentation/i2c/i2c-stub
parent1b3e5baa8850947b2cc15f323783ddb04dc4bffa (diff)
downloadlinux-b3af547e197fa3ca648d148dd8d36befe989e5a0.tar.gz
i2c-stub: Mention the existence of an helper script
There's a new script named i2c-stub-from-dump that can be very helpful when working with the i2c-stub driver. Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'Documentation/i2c/i2c-stub')
-rw-r--r--Documentation/i2c/i2c-stub3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/i2c/i2c-stub b/Documentation/i2c/i2c-stub
index 89e69ad3436..41889c091a3 100644
--- 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
+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]: