diff options
author | Luca Ceresoli <luca@lucaceresoli.net> | 2020-01-29 16:19:29 +0100 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2020-01-29 22:01:24 +0100 |
commit | 2f07c05f14a8bf5ee815e159a451d580d9113db9 (patch) | |
tree | 8a9d9df29daec1392238314a34b681354ba1f569 /Documentation/i2c/writing-clients.rst | |
parent | 020bc5b9296af6d3e0b255cff3a2674191287624 (diff) | |
download | linux-stable-2f07c05f14a8bf5ee815e159a451d580d9113db9.tar.gz linux-stable-2f07c05f14a8bf5ee815e159a451d580d9113db9.tar.bz2 linux-stable-2f07c05f14a8bf5ee815e159a451d580d9113db9.zip |
docs: i2c: call it "I2C" consistently
Uppercase "I2C" is used almost everywhere in the docs, but the lowercase
version "i2c" is used somewhere. Use the uppercase form consistently.
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Acked-by: Peter Rosin <peda@axentia.se>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'Documentation/i2c/writing-clients.rst')
-rw-r--r-- | Documentation/i2c/writing-clients.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/i2c/writing-clients.rst b/Documentation/i2c/writing-clients.rst index 0336909ca01b..44d97b2c9a82 100644 --- a/Documentation/i2c/writing-clients.rst +++ b/Documentation/i2c/writing-clients.rst @@ -95,7 +95,7 @@ to gather information from the client, or write new information to the client. I have found it useful to define foo_read and foo_write functions for this. -For some cases, it will be easier to call the i2c functions directly, +For some cases, it will be easier to call the I2C functions directly, but many chips have some kind of register-value idea that can easily be encapsulated. @@ -344,7 +344,7 @@ Plain I2C communication int i2c_master_recv(struct i2c_client *client, char *buf, int count); These routines read and write some bytes from/to a client. The client -contains the i2c address, so you do not have to include it. The second +contains the I2C address, so you do not have to include it. The second parameter contains the bytes to read/write, the third the number of bytes to read/write (must be less than the length of the buffer, also should be less than 64k since msg.len is u16.) Returned is the actual number of bytes |