2019-05-19 13:07:45 +01:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2017-11-08 19:30:38 -05:00
|
|
|
config VIDEO_IPU3_CIO2
|
|
|
|
|
tristate "Intel ipu3-cio2 driver"
|
media: Kconfig: cleanup VIDEO_DEV dependencies
media Kconfig has two entries associated to V4L API:
VIDEO_DEV and VIDEO_V4L2.
On Kernel 2.6.x, there were two V4L APIs, each one with its own flag.
VIDEO_DEV were meant to:
1) enable Video4Linux and make its Kconfig options to appear;
2) it makes the Kernel build the V4L core.
while VIDEO_V4L2 where used to distinguish between drivers that
implement the newer API and drivers that implemented the former one.
With time, such meaning changed, specially after the removal of
all V4L version 1 drivers.
At the current implementation, VIDEO_DEV only does (1): it enables
the media options related to V4L, that now has:
menu "Video4Linux options"
visible if VIDEO_DEV
source "drivers/media/v4l2-core/Kconfig"
endmenu
but it doesn't affect anymore the V4L core drivers.
The rationale is that the V4L2 core has a "soft" dependency
at the I2C bus, and now requires to select a number of other
Kconfig options:
config VIDEO_V4L2
tristate
depends on (I2C || I2C=n) && VIDEO_DEV
select RATIONAL
select VIDEOBUF2_V4L2 if VIDEOBUF2_CORE
default (I2C || I2C=n) && VIDEO_DEV
In the past, merging them would be tricky, but it seems that it is now
possible to merge those symbols, in order to simplify V4L dependencies.
Let's keep VIDEO_DEV, as this one is used on some make *defconfig
configurations.
Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com> # for meson-vdec & meson-ge2d
Acked-by: Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>
Acked-by: Łukasz Stelmach <l.stelmach@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
2022-03-13 07:25:46 +01:00
|
|
|
depends on VIDEO_DEV && PCI
|
2023-09-27 11:53:12 +03:00
|
|
|
depends on IPU_BRIDGE || !IPU_BRIDGE
|
2020-12-14 16:28:32 +01:00
|
|
|
depends on ACPI || COMPILE_TEST
|
|
|
|
|
depends on X86
|
media: Kconfig files: use select for V4L2 subdevs and MC
There are lots of drivers that only work when the media controller
and/or the V4L2 subdev APIs are present.
Right now, someone need to first enable those APIs before
using those drivers.
Well, ideally, drivers, should, instead *optionally*
depend on it, in order for PC camera drivers to be able to use
them, but nowadays most drivers are UVC cameras, with don't
require a sensor driver.
So, be it.
Let's instead make them select the MEDIA_CONTROLLER and the
SUBDEV API, in order to make easier for people to be able
of enabling them.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 15:36:56 +01:00
|
|
|
select MEDIA_CONTROLLER
|
|
|
|
|
select VIDEO_V4L2_SUBDEV_API
|
2017-11-08 19:30:38 -05:00
|
|
|
select V4L2_FWNODE
|
|
|
|
|
select VIDEOBUF2_DMA_SG
|
|
|
|
|
|
2019-03-20 06:39:44 -04:00
|
|
|
help
|
2018-05-02 19:19:29 -04:00
|
|
|
This is the Intel IPU3 CIO2 CSI-2 receiver unit, found in Intel
|
|
|
|
|
Skylake and Kaby Lake SoCs and used for capturing images and
|
|
|
|
|
video from a camera sensor.
|
2017-11-08 19:30:38 -05:00
|
|
|
|
2018-05-02 19:19:29 -04:00
|
|
|
Say Y or M here if you have a Skylake/Kaby Lake SoC with MIPI CSI-2
|
|
|
|
|
connected camera.
|
|
|
|
|
The module will be called ipu3-cio2.
|