From: Luca Ceresoli Date: Wed, 29 Jan 2020 15:19:53 +0000 (+0100) Subject: docs: i2c: writing-clients: properly name the stop condition X-Git-Tag: v5.6-rc1~31^2~8 X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=commitdiff_plain;h=4fcb445ec688a62da9c864ab05a4bd39b0307cdc;p=linux.git docs: i2c: writing-clients: properly name the stop condition In I2C there is no such thing as a "stop bit". Use the proper naming: "stop condition". Signed-off-by: Luca Ceresoli Reported-by: Jean Delvare Reviewed-by: Jean Delvare Signed-off-by: Wolfram Sang --- diff --git a/Documentation/i2c/writing-clients.rst b/Documentation/i2c/writing-clients.rst index 82aa33c964d3..978cc8210bf3 100644 --- a/Documentation/i2c/writing-clients.rst +++ b/Documentation/i2c/writing-clients.rst @@ -357,9 +357,9 @@ read/written. This sends a series of messages. Each message can be a read or write, and they can be mixed in any way. The transactions are combined: no -stop bit is sent between transaction. The i2c_msg structure contains -for each message the client address, the number of bytes of the message -and the message data itself. +stop condition is issued between transaction. The i2c_msg structure +contains for each message the client address, the number of bytes of the +message and the message data itself. You can read the file ``i2c-protocol`` for more information about the actual I2C protocol.