Kernel/linux
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git synced 2025-01-16 01:54:00 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Documentation: i2c: fix references to other documents

Browse Source 
Similar to commit fe99b819487d ("docs: i2c: i2c-sysfs: fix hyperlinks"),
make other links in documentation consistent with the preferred way.

Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
This commit is contained in:
Wolfram Sang 2022-09-13 11:05:52 +01:00 committed by Wolfram Sang
parent 2c2c72ec11
commit 9d55e7b0bd
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/i2c/dev-interface.rst
View File

@ -148,7 +148,7 @@ You can do plain I2C transactions by using read(2) and write(2) calls.
You do not need to pass the address byte; instead, set it through You do not need to pass the address byte; instead, set it through
ioctl I2C_SLAVE before you try to access the device. ioctl I2C_SLAVE before you try to access the device.
You can do SMBus level transactions (see documentation file smbus-protocol You can do SMBus level transactions (see documentation file smbus-protocol.rst
for details) through the following functions:: for details) through the following functions::
__s32 i2c_smbus_write_quick(int file, __u8 value); __s32 i2c_smbus_write_quick(int file, __u8 value);

6
Documentation/i2c/slave-interface.rst
View File

@ -32,9 +32,9 @@ User manual
=========== ===========
I2C slave backends behave like standard I2C clients. So, you can instantiate I2C slave backends behave like standard I2C clients. So, you can instantiate
them as described in the document 'instantiating-devices'. The only difference them as described in the document instantiating-devices.rst. The only
is that i2c slave backends have their own address space. So, you have to add difference is that i2c slave backends have their own address space. So, you
0x1000 to the address you would originally request. An example for have to add 0x1000 to the address you would originally request. An example for
instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64 instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64
on bus 1:: on bus 1::

4
Documentation/i2c/writing-clients.rst
View File

@ -364,7 +364,7 @@ stop condition is issued between transaction. The i2c_msg structure
contains for each message the client address, the number of bytes of the contains for each message the client address, the number of bytes of the
message and the message data itself. message and the message data itself.
You can read the file ``i2c-protocol`` for more information about the You can read the file i2c-protocol.rst for more information about the
actual I2C protocol. actual I2C protocol.
@ -414,7 +414,7 @@ transactions return 0 on success; the 'read' transactions return the read
value, except for block transactions, which return the number of values value, except for block transactions, which return the number of values
read. The block buffers need not be longer than 32 bytes. read. The block buffers need not be longer than 32 bytes.
You can read the file ``smbus-protocol`` for more information about the You can read the file smbus-protocol.rst for more information about the
actual SMBus protocol. actual SMBus protocol.