Lines Matching refs:be

6 Linux can also be an I2C slave if the I2C controller in use has slave
15 use a character device, be in-kernel only, or something completely different:
49 First, the events which are used by the bus driver and the backend will be
51 drivers and writing backends will be given.
62 types described hereafter. 'val' holds an u8 value for the data byte to be
63 read/written and is thus bidirectional. The pointer to val must always be
65 is the return value from the backend. Mandatory events must be provided by the
66 bus drivers and must be checked for by backend drivers.
75 Another I2C master wants to write data to us. This event should be sent once
78 to be done, though.
82 'val': backend returns first byte to be sent
85 Another I2C master wants to read data from us. This event should be sent once
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'
96 should be nacked.
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
109 needs to be sent again on the next I2C_SLAVE_READ_REQUEST, depending a bit on
118 reset its state machine for I2C transfers to be able to receive new requests.
142   should use pm_runtime_forbid() because your device usually needs to be powered
143   on always to be able to detect its slave address. When unregistering, do the
164 arises. However, cases should be extremely rare because the master is expected
173 bytes came up. Such an extension might be possible, usefulness is unclear at
176 * Buffers should be opt-in and slave drivers will always have to support
181   on writes an action should be immediately triggered. For reads, the data in
185   means additional code to handle this exception. Such code tends to be