Lines Matching +full:capture +full:- +full:only

1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
32   instance to any parallel video input or any MIPI-CSI front-end);
33 - runtime PM and system wide suspend/resume
36 -----------------------
38 - LCD writeback input
39 - per frame clock gating (mem-to-mem)
42 ---------------------
52 connections of the MIPI-CSIS device(s) to the FIMC entities.
56 viewfinder and still capture setup).
62 Memory-to-memory video node
65 V4L2 memory-to-memory interface at /dev/video? device node.  This is standalone
66 video device, it has no media pads. However please note the mem-to-mem and
67 capture video node operation on same FIMC instance is not allowed.  The driver
71 Capture video node
74 The driver supports V4L2 Video Capture Interface as defined at
77 At the capture and mem-to-mem video nodes only the multi-planar API is
78 supported. For more details see: :ref:`planar-apis`.
80 Camera capture subdevs
83 Each FIMC instance exports a sub-device node (/dev/v4l-subdev?), a sub-device
85 MIPI-CSI receiver device (currently up to two).
90 In order to enable more precise camera pipeline control through the sub-device
91 API the driver creates a sysfs entry associated with "s5p-fimc-md" platform
92 device. The entry path is: /sys/platform/devices/s5p-fimc-md/subdev_conf_mode.
94 In typical use case there could be a following capture pipeline configuration:
95 sensor subdev -> mipi-csi subdev -> fimc subdev -> video node
97 When we configure these devices through sub-device API at user space, the
101 When we don't use sub-device user space API the whole configuration of all
103 The sysfs entry allows to instruct the capture node driver not to configure
104 the sub-devices (format, crop), to avoid resetting the subdevs' configuration
107 For full sub-device control support (subdevs configured at user space before
110 .. code-block:: none
112 	# echo "sub-dev" > /sys/platform/devices/s5p-fimc-md/subdev_conf_mode
114 For V4L2 video node control only (subdevs configured internally by the host
117 .. code-block:: none
119 	# echo "vid-dev" > /sys/platform/devices/s5p-fimc-md/subdev_conf_mode
124 --------------------------------------------------
127 hardware - video capture and mem-to-mem and additionally a subdev node for
128 more precise FIMC capture subsystem control. In addition a separate v4l2
129 sub-device node is created per each MIPI-CSIS device.
131 How to find out which /dev/video? or /dev/v4l-subdev? is assigned to which
136 .. code-block:: none
138 	# dmesg | grep -i fimc
142 or retrieve the information from /dev/media? with help of the media-ctl tool:
144 .. code-block:: none
146 	# media-ctl -p
149 --------
152 two modules are created (in addition to the core v4l2 modules): s5p-fimc.ko and
153 optional s5p-csis.ko (MIPI-CSI receiver subdev).