Lines Matching +full:data +full:- +full:out
5 UCAN is the protocol used by the microcontroller-based USB-CAN
6 adapter that is integrated on System-on-Modules from Theobroma Systems
9 The UCAN protocol has been designed to be hardware-independent.
11 internally. All multi-byte integers are encoded as Little Endian.
25 The device sends CAN data frames and CAN error frames
27 OUT endpoint
28 The driver sends CAN data frames on the out endpoint
40 The driver uses ``ucan_ctrl_command_in/out`` and
44 ------------
51 ``wLength`` * Host to Device - Number of bytes to transmit
52 * Device to Host - Maximum Number of bytes to
58 --------------
64 ---------------
75 ------------------
169 --------------------------
185 A data packet on the USB IN endpoint contains one or more
187 data packet, the ``len`` field can be used to jump to the next
188 ``ucan_message_in`` value (take care to sanity-check the ``len`` value
189 against the actual data size).
194 -------------
196 Each ``ucan_message_in`` must be aligned to a 4-byte boundary (relative
197 to the start of the start of the data buffer). That means that there
202 +----------------------------+ < 0
206 +----------------------------+ < len
208 +----------------------------+ < round_up(len, 4)
212 +----------------------------+
216 --------------
226 Data received from the CAN bus (ID + payload).
235 list of of tuples <echo-ids, flags>.
237 The echo-id identifies the frame from (echos the id from a previous
243 ------------
252 OUT Message Format
255 A data packet on the USB OUT endpoint contains one or more ``struct
257 data packet, the device uses the ``len`` field to jump to the next
259 bytes (relative to the start of the data buffer). The mechanism is
264 +----------------------------+ < 0
268 +----------------------------+ < len
270 +----------------------------+ < round_up(len, 4)
274 +----------------------------+
278 --------------
288 Transmit a CAN frame. (parameters: ``id``, ``data``)
291 ------------
294 the *OUT* pipe until more buffers are available. The driver stops the
295 queue when a certain threshold of out packets are incomplete.
313 -------
315 - The device does not recover from bus of automatically.
316 - Bus OFF is indicated by an error frame (see ``uapi/linux/can/error.h``)
317 - Bus OFF recovery is started by ``UCAN_COMMAND_RESTART``
318 - Once Bus OFF recover is completed the device sends an error frame
319 indicating that it is on ERROR-ACTIVE state.
320 - During Bus OFF no frames are sent by the device.
321 - During Bus OFF transmission requests from the host are completed