Lines Matching refs:byte

62 types described hereafter. 'val' holds an u8 value for the data byte to be
82 'val': backend returns first byte to be sent
87 should transmit the first byte.
91 'val': bus driver delivers received byte
92 'ret': 0 if the byte should be acked, some errno if the byte should be nacked
94 Another I2C master has sent a byte to us which needs to be set in 'val'. If 'ret'
95 is zero, the bus driver should ack this byte. If 'ret' is an errno, then the byte
100 'val': backend returns next byte to be sent
103 The bus driver requests the next byte to be sent to another I2C master in
104 'val'. Important: This does not mean that the previous byte has been acked, it
105 only means that the previous byte is shifted out to the bus! To ensure seamless
106 transmission, most hardware requests the next byte when the previous one is
107 still shifted out. If the master sends NACK and stops reading after the byte
108 currently shifted out, this byte requested here is never used. It very likely
163 byte when it reads from us. We could make this an optional event if the need
177   byte-based transactions as the ultimate fallback because this is how the