Lines Matching +full:fimc +full:- +full:is
1 .. SPDX-License-Identifier: GPL-2.0
5 The Samsung S5P/Exynos4 FIMC driver
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
10 The FIMC (Fully Interactive Mobile Camera) device available in Samsung
11 SoC Application Processors is an integrated camera host interface, color
14 path. There are multiple FIMC instances in the SoCs (up to 4), having
16 availability, LCD writeback support, etc. The driver is located at
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 ---------------------
48 The media device driver name is "Samsung S5P FIMC".
50 The purpose of this interface is to allow changing assignment of FIMC instances
52 connections of the MIPI-CSIS device(s) to the FIMC entities.
55 data from the sensor through more than one FIMC instance (e.g. for simultaneous
58 Reconfiguration is done by enabling/disabling media links created by the driver
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
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`.
83 Each FIMC instance exports a sub-device node (/dev/v4l-subdev?), a sub-device
84 node is also created per each available and enabled at the platform level
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.
95 sensor subdev -> mipi-csi subdev -> fimc subdev -> video node
97 When we configure these devices through sub-device API at user space, the
98 configuration flow must be from left to right, and the video node is
101 When we don't use sub-device user space API the whole configuration of all
102 devices belonging to the pipeline is done at the video node driver.
104 the sub-devices (format, crop), to avoid resetting the subdevs' configuration
105 when the last configuration steps at the video node is performed.
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
117 .. code-block:: none
119 # echo "vid-dev" > /sys/platform/devices/s5p-fimc-md/subdev_conf_mode
121 This is a default option.
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 --------
151 If the driver is built as a loadable kernel module (CONFIG_VIDEO_SAMSUNG_S5P_FIMC=m)
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).