Proxmox-Port/linux-loongson
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson synced 2025-08-30 21:52:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: i2c: summary: start sentences consistently.

Browse Source 
Change the first paragraphs to contain only one space after the end of
the previous sentence like in the rest of the document.

Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
This commit is contained in:
Wolfram Sang 2024-06-21 09:30:08 +02:00
parent 1cbf347288
commit d18b822c8f
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/i2c/summary.rst
View File

@ -4,10 +4,10 @@ Introduction to I2C and SMBus
I²C (pronounce: I squared C and written I2C in the kernel documentation) is 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 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 speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides
an inexpensive bus for connecting many types of devices with infrequent or an inexpensive bus for connecting many types of devices with infrequent or
low bandwidth communications needs. I2C is widely used with embedded low bandwidth communications needs. I2C is widely used with embedded
systems. Some systems use variants that don't meet branding requirements, systems. Some systems use variants that don't meet branding requirements,
and so are not advertised as being I2C but come under different names, and so are not advertised as being I2C but come under different names,
e.g. TWI (Two Wire Interface), IIC. e.g. TWI (Two Wire Interface), IIC.
@ -18,14 +18,14 @@ access the PDF. An older version of the specification (revision 6) is archived
`here <https://web.archive.org/web/20210813122132/https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_. `here <https://web.archive.org/web/20210813122132/https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_.
SMBus (System Management Bus) is based on the I2C protocol, and is mostly SMBus (System Management Bus) is based on the I2C protocol, and is mostly
a subset of I2C protocols and signaling. Many I2C devices will work on an a subset of I2C protocols and signaling. Many I2C devices will work on an
SMBus, but some SMBus protocols add semantics beyond what is required to SMBus, but some SMBus protocols add semantics beyond what is required to
achieve I2C branding. Modern PC mainboards rely on SMBus. The most common achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
devices connected through SMBus are RAM modules configured using I2C EEPROMs, devices connected through SMBus are RAM modules configured using I2C EEPROMs,
and hardware monitoring chips. and hardware monitoring chips.
Because the SMBus is mostly a subset of the generalized I2C bus, we can Because the SMBus is mostly a subset of the generalized I2C bus, we can
use its protocols on many I2C systems. However, there are systems that don't use its protocols on many I2C systems. However, there are systems that don't
meet both SMBus and I2C electrical constraints; and others which can't meet both SMBus and I2C electrical constraints; and others which can't
implement all the common SMBus protocol semantics or messages. implement all the common SMBus protocol semantics or messages.