Lines Matching refs:with

24    it is possible.  Unfortunately, it is not always possible; working with
29    contiguous; buffers allocated with vmalloc(), in other words.  These
36    controllers cannot deal with anything else.
38 Videobuf can work with all three types of buffers, but the driver author
61 along with a list_head for the queue of available buffers.  There will also
65 The next step is to write four simple callbacks to help videobuf deal with
103 VIDEOBUF_QUEUED.  Note that this function is called with the queue spinlock
181 applications have a chance of working with the device.  Videobuf makes it
182 easy to do that with the same code.  To implement read(), the driver need
202 The poll() function can usually be implemented with a direct call to:
209 with the first available buffer.
239 - those associated with streaming I/O - turn almost directly into videobuf
258 complex, of course, since they will also need to deal with starting and
284 populate it with pointers to the pieces of the allocated buffer; sglen
288 with buffer allocation at all; videobuf will handle those details.  The
290 allocate the buffers (with dma_alloc_coherent()) when it sees fit.  That
294 currently play well with those drivers.
296 As of 2.6.31, contiguous-DMA drivers can work with a user-supplied buffer,
299 kernel drivers, or those contained within huge pages, will work with these
324 done field (a wait_queue_head_t structure) with waitqueue_active().
327 DMA; that ensures that the videobuf layer will not try to do anything with
332 can get a memory pointer with:
354 enough to get started with.  Note also that all of these calls are exported