summaryrefslogtreecommitdiff
path: root/drivers/char/Makefile
diff options
context:
space:
mode:
authorFancy Fang <chen.fang@freescale.com>2014-10-10 06:21:22 +0400
committerMauro Carvalho Chehab <mchehab@osg.samsung.com>2014-10-24 15:32:41 +0400
commit8a6a547fe1b13fe3e523b3f076f8295dd03a7c41 (patch)
treea4b0185ee0b20b2f0953c752ecd55fc66cfc1006 /drivers/char/Makefile
parentf2d90e6479ab199f568dc16cba0813e47e8b1d95 (diff)
downloadlinux-8a6a547fe1b13fe3e523b3f076f8295dd03a7c41.tar.xz
[media] videobuf-dma-contig: set vm_pgoff to be zero to pass the sanity check in vm_iomap_memory()
When user requests V4L2_MEMORY_MMAP type buffers, the videobuf-core will assign the corresponding offset to the 'boff' field of the videobuf_buffer for each requested buffer sequentially. Later, user may call mmap() to map one or all of the buffers with the 'offset' parameter which is equal to its 'boff' value. Obviously, the 'offset' value is only used to find the matched buffer instead of to be the real offset from the buffer's physical start address as used by vm_iomap_memory(). So, in some case that if the offset is not zero, vm_iomap_memory() will fail. Signed-off-by: Fancy Fang <chen.fang@freescale.com> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Diffstat (limited to 'drivers/char/Makefile')
0 files changed, 0 insertions, 0 deletions