aboutsummaryrefslogtreecommitdiffstats
path: root/include/media/videobuf2-vmalloc.h
diff options
context:
space:
mode:
authorSylwester Nawrocki <s.nawrocki@samsung.com>2011-09-01 06:01:08 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2011-09-06 17:35:52 -0300
commitd3953223b0905437fef7ce60506b5fdfaf98dda6 (patch)
tree12570704e36b7131a03ec31f0746ae459410d251 /include/media/videobuf2-vmalloc.h
parent[media] s5p-fimc: Remove v4l2_device from video capture and m2m driver (diff)
downloadlinux-dev-d3953223b0905437fef7ce60506b5fdfaf98dda6.tar.xz
linux-dev-d3953223b0905437fef7ce60506b5fdfaf98dda6.zip
[media] s5p-fimc: Add the media device driver
Add a top level media device driver aggregating FIMC video devnodes, MIPI-CSIS and sensor subdevs. This driver gathers all media entities and creates the possible links between them during initialization. By default some links will be activated to enable access to all available sensors in the system. For example if there are sensors S0, S1 listed in the media device platform data definition they will be by default assigned to FIMC0, FIMC1 respectively, which in turn will corresponds to separate /dev/video?. There is enough FIMC H/W entities to cover all available physical camera interfaces in the system. The fimc media device driver is bound to the "s5p-fimc-md" platform device. Such platform device should be created by board initialization code and camera sensors description array need to be specified as its platform data. The media device driver also implements various video pipeline operations, for enabling subdevs power, streaming, etc., which will be used by the capture video node driver. Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'include/media/videobuf2-vmalloc.h')
0 files changed, 0 insertions, 0 deletions