Lines Matching +full:subset +full:- +full:of
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).
8 this package are briefly described at the end of this document.
11 which is a subset from the I2C protocol. Fortunately, many devices use
12 only the same subset, which makes it possible to put them on an SMBus.
15 commands if at all possible (if the device uses only that subset of the
21 Below is a list of SMBus protocol operations, and the functions executing
23 don't match these function names. For some of the operations which pass a
49 high byte of a 16 bit word.
50 Count (8 bits) A data byte containing the length of a block operation.
60 This sends a single bit to the device, at the place of the Rd/Wr bit::
87 This operation is the reverse of Receive Byte: it sends a single byte
134 register is specified through the Comm byte. This is the opposite of
149 This is the opposite of the Read Word operation. 16 bits
150 of data are written to a device, to the designated register that is
166 16 bits of data to it, and reads 16 bits of data in return::
179 This command reads a block of up to 32 bytes from a device, from a
181 of data is specified by the device in the Count byte.
196 The opposite of the Block Read command, this writes up to 32 bytes to
198 Comm byte. The amount of data is specified in the Count byte.
207 SMBus Block Write - Block Read Process Call
210 SMBus Block Write - Block Read Process Call was introduced in
211 Revision 2.0 of the specification.
214 1 to 31 bytes of data to it, and reads 1 to 31 bytes of data in return::
241 client->irq assigned to a Host Notify IRQ if no one else specified another.
249 Packet Error Checking was introduced in Revision 1.1 of the specification.
251 PEC adds a CRC-8 error-checking byte to transfers using it, immediately
258 The Address Resolution Protocol was introduced in Revision 2.0 of
259 the specification. It is a higher-layer protocol which uses the
270 SMBus Alert was introduced in Revision 1.0 of the specification.
292 I2C block transactions do not limit the number of bytes transferred
293 but the SMBus layer places a limit of 32 bytes.
301 This command reads a block of bytes from a device, from a
315 The opposite of the Block Read command, this writes bytes to
317 Comm byte. Note that command lengths of 0, 2, or more bytes are