From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: Easwar Hariharan <eahariha@linux.microsoft.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Shyti <andi.shyti@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v3 3/6] docs: i2c: summary: update speed mode description
Date: Fri, 14 Jun 2024 10:12:41 +0200 [thread overview]
Message-ID: <20240614081239.7128-11-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20240614081239.7128-8-wsa+renesas@sang-engineering.com>
Fastest I2C mode is 5 MHz. Update the docs and reword the paragraph
slightly.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
---
Documentation/i2c/summary.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst
index e3ab1d414014..a1e5c0715f8b 100644
--- a/Documentation/i2c/summary.rst
+++ b/Documentation/i2c/summary.rst
@@ -3,8 +3,8 @@ Introduction to I2C and SMBus
=============================
I²C (pronounce: I squared C and written I2C in the kernel documentation) is
-a protocol developed by Philips. It is a slow two-wire protocol (variable
-speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides
+a protocol developed by Philips. It is a two-wire protocol with variable
+speed (typically up to 400 kHz, high speed modes up to 5 MHz). It provides
an inexpensive bus for connecting many types of devices with infrequent or
low bandwidth communications needs. I2C is widely used with embedded
systems. Some systems use variants that don't meet branding requirements,
--
2.43.0
next prev parent reply other threads:[~2024-06-14 8:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 8:12 [PATCH v3 0/6] docs: i2c: summary: update and use inclusive wording Wolfram Sang
2024-06-14 8:12 ` [PATCH v3 1/6] docs: i2c: summary: start sentences consistently Wolfram Sang
2024-06-15 17:47 ` Andi Shyti
2024-06-14 8:12 ` [PATCH v3 2/6] docs: i2c: summary: update I2C specification link Wolfram Sang
2024-06-15 17:48 ` Andi Shyti
2024-06-14 8:12 ` Wolfram Sang [this message]
2024-06-15 18:07 ` [PATCH v3 3/6] docs: i2c: summary: update speed mode description Andi Shyti
2024-06-14 8:12 ` [PATCH v3 4/6] docs: i2c: summary: document use of inclusive language Wolfram Sang
2024-06-15 18:12 ` Andi Shyti
2024-06-14 8:12 ` [PATCH v3 5/6] docs: i2c: summary: document 'local' and 'remote' targets Wolfram Sang
2024-06-15 20:49 ` Andi Shyti
2024-06-16 19:14 ` Wolfram Sang
2024-06-17 11:58 ` Andi Shyti
2024-06-17 16:45 ` Wolfram Sang
2024-06-17 16:57 ` Easwar Hariharan
2024-06-17 19:25 ` Andi Shyti
2024-06-19 7:10 ` Wolfram Sang
2024-06-20 16:05 ` Easwar Hariharan
2024-06-20 23:39 ` Andi Shyti
2024-06-20 23:38 ` Andi Shyti
2024-06-21 7:03 ` Wolfram Sang
2024-06-14 8:12 ` [PATCH v3 6/6] docs: i2c: summary: be clearer with 'controller/target' and 'adapter/client' pairs Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240614081239.7128-11-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=eahariha@linux.microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).