Lines Matching full:backend

9 a hardware independent software backend providing the actual functionality. An
13 needed. The backend driver and the I2C bus driver communicate via events. Here
15 transported. The dotted line marks only one example. The backend could also
21   | Userspace +........+ Backend +-----------+ Driver +-----+ Controller |
27 Note: Technically, there is also the I2C core between the backend and the
43 Each backend should come with separate documentation to describe its specific
50 First, the events which are used by the bus driver and the backend will be
58 The bus driver sends an event to the backend using the following function::
66 is the return value from the backend. Mandatory events must be provided by the
67 bus drivers and must be checked for by backend drivers.
75   'ret': 0 if the backend is ready, otherwise some errno
80 always ack the address phase. If 'ret' is zero, backend initialization or
87   'val': backend returns first byte to be sent
107   'val': backend returns next byte to be sent
118 your backend, though.
126 A stop condition was received. This can happen anytime and the backend should
133 If you want to write a software backend:
155 * Catch the slave interrupts and send appropriate i2c_slave_events to the backend.
190 * Buffers should be opt-in and backend drivers will always have to support
196   For reads, the data kept in the buffer might get stale if the backend just