Lines Matching refs:drivers

44 shows up occasionally in system-on-chip drivers where the performance
113     /* Scatter/gather drivers */
118     /* vmalloc drivers */
121     /* Contiguous drivers */
178 V4L2 capture drivers can be written to support either of two APIs: the
213 V4L2 drivers, the often-complex mmap() implementation simplifies to a
255 boilerplate in a lot of V4L2 drivers.
289 same is normally true of contiguous-DMA drivers as well; videobuf will
291 means that these drivers may be trying to do high-order allocations at any
292 time, an operation which is not always guaranteed to work.  Some drivers
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
300 drivers.
307 drivers, this process works approximately as follows:
330 For scatter/gather drivers, the needed memory pointers will be found in the
336 For contiguous DMA drivers, the function to use is:
341 of the DMA buffer from drivers.
352 (drivers/media/platform/vivi.c), which is maintained as an example of how V4L2
353 drivers should be written.  Vivi only uses the vmalloc() API, but it's good