Lines Matching +full:sub +full:- +full:nodes
1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/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 ------------------
44 - media device driver
45 drivers/media/platform/exynos4-is/media-dev.[ch]
47 - camera capture video device driver
48 drivers/media/platform/exynos4-is/fimc-capture.c
50 - MIPI-CSI2 receiver subdev
51 drivers/media/platform/exynos4-is/mipi-csis.[ch]
53 - video post-processor (mem-to-mem)
54 drivers/media/platform/exynos4-is/fimc-core.c
56 - common files
57 drivers/media/platform/exynos4-is/fimc-core.h
58 drivers/media/platform/exynos4-is/fimc-reg.h
59 drivers/media/platform/exynos4-is/regs-fimc.h
62 ---------------------
72 connections of the MIPI-CSIS device(s) to the FIMC entities.
81 Memory-to-memory video node
84 V4L2 memory-to-memory interface at /dev/video? device node. This is standalone
85 video device, it has no media pads. However please note the mem-to-mem and
96 At the capture and mem-to-mem video nodes only the multi-planar API is
97 supported. For more details see: :ref:`planar-apis`.
102 Each FIMC instance exports a sub-device node (/dev/v4l-subdev?), a sub-device
104 MIPI-CSI receiver device (currently up to two).
109 In order to enable more precise camera pipeline control through the sub-device
110 API the driver creates a sysfs entry associated with "s5p-fimc-md" platform
111 device. The entry path is: /sys/platform/devices/s5p-fimc-md/subdev_conf_mode.
114 sensor subdev -> mipi-csi subdev -> fimc subdev -> video node
116 When we configure these devices through sub-device API at user space, the
119 When we don't use sub-device user space API the whole configuration of all
122 the sub-devices (format, crop), to avoid resetting the subdevs' configuration
125 For full sub-device control support (subdevs configured at user space before
128 .. code-block:: none
130 # echo "sub-dev" > /sys/platform/devices/s5p-fimc-md/subdev_conf_mode
135 .. code-block:: none
137 # echo "vid-dev" > /sys/platform/devices/s5p-fimc-md/subdev_conf_mode
141 5. Device mapping to video and subdev device nodes
142 --------------------------------------------------
144 There are associated two video device nodes with each device instance in
145 hardware - video capture and mem-to-mem and additionally a subdev node for
147 sub-device node is created per each MIPI-CSIS device.
149 How to find out which /dev/video? or /dev/v4l-subdev? is assigned to which
154 .. code-block:: none
156 # dmesg | grep -i fimc
158 (note that udev, if present, might still have rearranged the video nodes),
160 or retrieve the information from /dev/media? with help of the media-ctl tool:
162 .. code-block:: none
164 # media-ctl -p
167 --------
170 two modules are created (in addition to the core v4l2 modules): s5p-fimc.ko and
171 optional s5p-csis.ko (MIPI-CSI receiver subdev).