Lines Matching full:byte

63 types described hereafter. 'val' holds an u8 value for the data byte to be
84   'val': backend returns first byte to be sent
90 should transmit the first byte.
94   'val': bus driver delivers received byte
96   'ret': 0 if the byte should be acked, some errno if the byte should be nacked
98 Another I2C master has sent a byte to us which needs to be set in 'val'. If 'ret'
99 is zero, the bus driver should ack this byte. If 'ret' is an errno, then the byte
104   'val': backend returns next byte to be sent
108 The bus driver requests the next byte to be sent to another I2C master in
109 'val'. Important: This does not mean that the previous byte has been acked, it
110 only means that the previous byte is shifted out to the bus! To ensure seamless
111 transmission, most hardware requests the next byte when the previous one is
112 still shifted out. If the master sends NACK and stops reading after the byte
113 currently shifted out, this byte requested here is never used. It very likely
174 byte when it reads from us. We could make this an optional event if the need
188   byte-based transactions as the ultimate fallback anyhow because this is how
192   because after each byte written an action should be immediately triggered.