Re: [PATCH v2 28/28] docs: i2c: writing-clients: properly name the stop condition
From: Jean Delvare <hidden>
Date: 2020-01-24 16:01:14
Also in:
linux-i2c, lkml
On Thu, 23 Jan 2020 15:56:26 +0100, Luca Ceresoli wrote:
quoted hunk ↗ jump to hunk
In I2C there is no such thing as a "stop bit". Use the proper naming: "stop condition". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Reported-by: Jean Delvare <redacted> --- This patch is new in v2. --- Documentation/i2c/writing-clients.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)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.
Reviewed-by: Jean Delvare <redacted> I have reviewed the whole v2 series, so any patch to which I did not reply to retains my Reviewed-by tag. Thanks Luca! -- Jean Delvare SUSE L3 Support