omap4_camera: Migrate to videobuf2
authorSergio Aguirre <saaguirre@ti.com>
Tue, 24 May 2011 19:01:53 +0000 (14:01 -0500)
committerSergio Aguirre <saaguirre@ti.com>
Tue, 24 May 2011 19:07:45 +0000 (14:07 -0500)
commit7d208908f553e6c30d37a9e050c210a2adbbeb21
treed2681057ef0892c3174a85f7a3875f0ab0a1f17f
parentf26816640ab20f9eb83962cfa878b90e9ebbd829
omap4_camera: Migrate to videobuf2

Move to videobuf2 library, BUT with 2 regressions:

- USERPTR is not supported now:

Reason is because in the new videobuf2 functions didn't look
very clear how to support USERPTR, and run them through the
custom "evenly separated physical pages" test, to be able
to use other's driver MMAP'd address, passed as USERPTR to us.

- Remove custom mmap function to use ISS_PREALLOC space:

Reason is to stick with current available frameworks, without
depending on a major unaccepted patchset for now (like CMA).

Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
drivers/media/video/Kconfig
drivers/media/video/omap4_camera.c