2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2017-11-09 00:30:38 +00:00
|
|
|
config VIDEO_IPU3_CIO2
|
|
|
|
|
tristate "Intel ipu3-cio2 driver"
|
|
|
|
|
depends on VIDEO_V4L2 && PCI
|
2018-04-20 17:42:50 +00:00
|
|
|
depends on (X86 && ACPI) || COMPILE_TEST
|
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 14:36:56 +00:00
|
|
|
select MEDIA_CONTROLLER
|
|
|
|
|
select VIDEO_V4L2_SUBDEV_API
|
2017-11-09 00:30:38 +00:00
|
|
|
select V4L2_FWNODE
|
|
|
|
|
select VIDEOBUF2_DMA_SG
|
|
|
|
|
|
2019-03-20 10:39:44 +00:00
|
|
|
help
|
2018-05-02 23:19:29 +00: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-09 00:30:38 +00:00
|
|
|
|
2018-05-02 23:19:29 +00: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.
|
