Lines Matching +full:i2c +full:- +full:protocol

2 The SMBus Protocol
5 The following is a summary of the SMBus protocol. It applies to
6 all revisions of the protocol (1.0, 1.1, and 2.0).
7 Certain protocol features which are not supported by
10 Some adapters understand only the SMBus (System Management Bus) protocol,
11 which is a subset from the I2C protocol. Fortunately, many devices use
14 If you write a driver for some I2C device, please try to use the SMBus
16 I2C protocol). This makes it possible to use the device driver on both
17 SMBus adapters and I2C adapters (the SMBus command set is automatically
18 translated to I2C on I2C adapters, but plain I2C commands can not be
21 Below is a list of SMBus protocol operations, and the functions executing
22 them.  Note that the names used in the SMBus protocol specifications usually
24 single data byte, the functions using SMBus protocol operation names execute
25 a different protocol operation entirely.
29 the corresponding functionality flag to ensure that the underlying I2C
31 Documentation/i2c/functionality.rst for the details.
44 Addr  (7 bits)  I2C 7 bit address. Note that this can be expanded to
45                 get a 10 bit I2C address.
52 [..]            Data sent by I2C device, as opposed to data sent by the host
207 SMBus Block Write - Block Read Process Call
210 SMBus Block Write - Block Read Process Call was introduced in
236 * I2C bus drivers which support SMBus Host Notify should report
238 * I2C bus drivers trigger SMBus Host Notify by a call to
240 * I2C drivers for devices which can trigger SMBus Host Notify will have
241   client->irq assigned to a Host Notify IRQ if no one else specified another.
251 PEC adds a CRC-8 error-checking byte to transfers using it, immediately
255 Address Resolution Protocol (ARP)
258 The Address Resolution Protocol was introduced in Revision 2.0 of
259 the specification. It is a higher-layer protocol which uses the
263 the protocol. All ARP communications use slave address 0x61 and
272 The SMBus alert protocol allows several SMBus slave devices to share a
278 * I2C bus drivers which support SMBus alert should call
280 * I2C drivers for devices which can trigger SMBus alerts should implement
284 I2C Block Transactions
287 The following I2C block transactions are similar to the SMBus Block Read
292 I2C block transactions do not limit the number of bytes transferred
296 I2C Block Read
310 I2C Block Write