Lines Matching refs:should

52 Depending on which type of buffers are being used, the driver should
59 The driver's data structure describing a V4L2 device should include a
82 parameter will be a suggested number of buffers to use; the driver should
86 device.  The size parameter should be set to the expected (maximum) size
90 passed to buf_prepare(), which should set the buffer's size, width, height,
92 VIDEOBUF_NEEDS_INIT, the driver should pass it to:
98 Finally, the buf_prepare() function should set the buffer's state to
101 When a buffer is queued for I/O, it is passed to buf_queue(), which should
110 used.  The driver should ensure that there is no I/O active on the buffer,
130 should be used (it should be zero in the buf_release() case), and intr
271 If the driver needs to do its own memory allocation, it should be done in
285 should be set to the length of the array.
320 vmalloc() case especially.  So the driver should be prepared for the list
322 buffer; the driver should not remove it from the list or fill it until a
326 A buffer's state should be set to VIDEOBUF_ACTIVE before being mapped for
346 buffer is owned by the videobuf layer and the driver should not touch it
353 drivers should be written.  Vivi only uses the vmalloc() API, but it's good