aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/i2c
diff options
context:
space:
mode:
authorDavid Brownell <david-b@pacbell.net>2008-07-14 22:38:23 +0200
committerJean Delvare <khali@mahadeva.delvare>2008-07-14 22:38:23 +0200
commit24a5bb7b1838dc4524dd353224e2aa09c22cac3b (patch)
tree8e7c7bb65b889e20d7a1067d41157b4b150cf045 /Documentation/i2c
parent75415490d6adc1aecbf0cade0785b007957d0cfe (diff)
downloadkernel_samsung_crespo-24a5bb7b1838dc4524dd353224e2aa09c22cac3b.zip
kernel_samsung_crespo-24a5bb7b1838dc4524dd353224e2aa09c22cac3b.tar.gz
kernel_samsung_crespo-24a5bb7b1838dc4524dd353224e2aa09c22cac3b.tar.bz2
i2c-core: Return -Errno, not -1
More updates to the I2C stack's fault reporting: make the core stop returning "-1" (usually "-EPERM") for all faults. Instead, pass lower level fault code up the stack, or return some appropriate errno. This patch happens to touch almost exclusively SMBus calls. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'Documentation/i2c')
-rw-r--r--Documentation/i2c/writing-clients8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/i2c/writing-clients b/Documentation/i2c/writing-clients
index d4cd412..ba5d197 100644
--- a/Documentation/i2c/writing-clients
+++ b/Documentation/i2c/writing-clients
@@ -598,10 +598,10 @@ be added back later if needed:
u8 command, u8 length,
u8 *values)
-All these transactions return -1 on failure. The 'write' transactions
-return 0 on success; the 'read' transactions return the read value, except
-for read_block, which returns the number of values read. The block buffers
-need not be longer than 32 bytes.
+All these transactions return a negative errno value on failure. The 'write'
+transactions return 0 on success; the 'read' transactions return the read
+value, except for block transactions, which return the number of values
+read. The block buffers need not be longer than 32 bytes.
You can read the file `smbus-protocol' for more information about the
actual SMBus protocol.