Lines Matching refs:be

6 Linux can also be an I2C slave in case I2C controllers have slave support.
14 example. The backend could also use e.g. a character device, be in-kernel
54 types described hereafter. 'val' holds an u8 value for the data byte to be
55 read/written and is thus bidirectional. The pointer to val must always be
57 is the return value from the backend. Mandatory events must be provided by the
58 bus drivers and must be checked for by backend drivers.
67 Another I2C master wants to write data to us. This event should be sent once
70 to be done, though.
74 'val': backend returns first byte to be sent
77 Another I2C master wants to read data from us. This event should be sent once
84 'ret': 0 if the byte should be acked, some errno if the byte should be nacked
86 Another I2C master has sent a byte to us which needs to be set in 'val'. If 'ret'
88 should be nacked.
92 'val': backend returns next byte to be sent
95 The bus driver requests the next byte to be sent to another I2C master in
101 needs to be sent again on the next I2C_SLAVE_READ_REQUEST, depending a bit on
110 reset its state machine for I2C transfers to be able to receive new requests.
134   should use pm_runtime_forbid() because your device usually needs to be powered
135   on always to be able to detect its slave address. When unregistering, do the
156 arises. However, cases should be extremely rare because the master is expected
165 bytes came up. Such an extension might be possible, usefulness is unclear at
168 * Buffers should be opt-in and slave drivers will always have to support
173   on writes an action should be immediately triggered. For reads, the data in
177   means additional code to handle this exception. Such code tends to be