2019-05-19 15:07:45 +03:00
# SPDX-License-Identifier: GPL-2.0-only
2012-08-14 23:23:43 +04:00
#
# Multimedia Video device configuration
#
if VIDEO_V4L2
2020-04-15 16:39:38 +03:00
comment "IR I2C driver auto-selected by 'Autoselect ancillary drivers'"
depends on MEDIA_SUBDRV_AUTOSELECT && I2C && RC_CORE
2012-08-14 23:23:43 +04:00
config VIDEO_IR_I2C
2019-01-11 18:49:51 +03:00
tristate "I2C module for IR" if !MEDIA_SUBDRV_AUTOSELECT || EXPERT
2012-08-14 23:23:43 +04:00
depends on I2C && RC_CORE
default y
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Most boards have an IR chip directly connected via GPIO. However,
some video boards have the IR connected via I2C bus.
If your board doesn't have an I2C IR chip, you may disable this
option.
In doubt, say Y.
#
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 17:36:56 +03:00
# V4L2 I2C drivers that aren't related with Camera support
2012-08-14 23:23:43 +04:00
#
2020-04-15 16:39:38 +03:00
comment "audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'"
2019-07-27 16:31:29 +03:00
depends on MEDIA_HIDE_ANCILLARY_SUBDRV
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 17:36:56 +03:00
#
# Encoder / Decoder module configuration
#
2020-04-15 16:39:38 +03:00
menu "Audio decoders, processors and mixers"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2012-08-14 23:23:43 +04:00
config VIDEO_TVAUDIO
tristate "Simple audio decoder chips"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for several audio decoder chips found on some bt8xx boards:
Philips: tda9840, tda9873h, tda9874h/a, tda9850, tda985x, tea6300,
tea6320, tea6420, tda8425, ta8874z.
Microchip: pic16c54 based design on ProVideo PV951 board.
To compile this driver as a module, choose M here: the
module will be called tvaudio.
config VIDEO_TDA7432
tristate "Philips TDA7432 audio processor"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for tda7432 audio decoder chip found on some bt8xx boards.
To compile this driver as a module, choose M here: the
module will be called tda7432.
config VIDEO_TDA9840
tristate "Philips TDA9840 audio processor"
depends on I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for tda9840 audio decoder chip found on some Zoran boards.
To compile this driver as a module, choose M here: the
module will be called tda9840.
2018-02-15 20:55:34 +03:00
config VIDEO_TDA1997X
tristate "NXP TDA1997x HDMI receiver"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
2018-02-23 16:13:26 +03:00
depends on SND_SOC
2018-10-03 00:12:43 +03:00
select HDMI
2019-03-18 19:40:05 +03:00
select SND_PCM
select V4L2_FWNODE
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 17:36:56 +03:00
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2018-02-15 20:55:34 +03:00
V4L2 subdevice driver for the NXP TDA1997x HDMI receivers.
To compile this driver as a module, choose M here: the
module will be called tda1997x.
2012-08-14 23:23:43 +04:00
config VIDEO_TEA6415C
tristate "Philips TEA6415C audio processor"
depends on I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for tea6415c audio decoder chip found on some bt8xx boards.
To compile this driver as a module, choose M here: the
module will be called tea6415c.
config VIDEO_TEA6420
tristate "Philips TEA6420 audio processor"
depends on I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for tea6420 audio decoder chip found on some bt8xx boards.
To compile this driver as a module, choose M here: the
module will be called tea6420.
config VIDEO_MSP3400
tristate "Micronas MSP34xx audio decoders"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Micronas MSP34xx series of audio decoders.
To compile this driver as a module, choose M here: the
module will be called msp3400.
2015-11-30 23:05:54 +03:00
config VIDEO_CS3308
tristate "Cirrus Logic CS3308 audio ADC"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2015-11-30 23:05:54 +03:00
Support for the Cirrus Logic CS3308 High Performance 8-Channel
Analog Volume Control
To compile this driver as a module, choose M here: the
module will be called cs3308.
2012-08-14 23:23:43 +04:00
config VIDEO_CS5345
tristate "Cirrus Logic CS5345 audio ADC"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Cirrus Logic CS5345 24-bit, 192 kHz
stereo A/D converter.
To compile this driver as a module, choose M here: the
module will be called cs5345.
config VIDEO_CS53L32A
tristate "Cirrus Logic CS53L32A audio ADC"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Cirrus Logic CS53L32A low voltage
stereo A/D converter.
To compile this driver as a module, choose M here: the
module will be called cs53l32a.
config VIDEO_TLV320AIC23B
tristate "Texas Instruments TLV320AIC23B audio codec"
2012-09-03 17:16:34 +04:00
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Texas Instruments TLV320AIC23B audio codec.
To compile this driver as a module, choose M here: the
module will be called tlv320aic23b.
2013-03-09 14:20:12 +04:00
config VIDEO_UDA1342
tristate "Philips UDA1342 audio codec"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2013-03-09 14:20:12 +04:00
Support for the Philips UDA1342 audio codec.
To compile this driver as a module, choose M here: the
module will be called uda1342.
2012-08-14 23:23:43 +04:00
config VIDEO_WM8775
tristate "Wolfson Microelectronics WM8775 audio ADC with input mixer"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Wolfson Microelectronics WM8775 high
performance stereo A/D Converter with a 4 channel input mixer.
To compile this driver as a module, choose M here: the
module will be called wm8775.
config VIDEO_WM8739
tristate "Wolfson Microelectronics WM8739 stereo audio ADC"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Wolfson Microelectronics WM8739
stereo A/D Converter.
To compile this driver as a module, choose M here: the
module will be called wm8739.
config VIDEO_VP27SMPX
2013-03-22 18:13:58 +04:00
tristate "Panasonic VP27's internal MPX"
2012-08-14 23:23:43 +04:00
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the internal MPX of the Panasonic VP27s tuner.
To compile this driver as a module, choose M here: the
module will be called vp27smpx.
2013-03-22 18:13:58 +04:00
config VIDEO_SONY_BTF_MPX
tristate "Sony BTF's internal MPX"
depends on VIDEO_V4L2 && I2C
help
Support for the internal MPX of the Sony BTF-PG472Z tuner.
To compile this driver as a module, choose M here: the
module will be called sony-btf-mpx.
2020-04-15 16:39:38 +03:00
endmenu
2013-03-22 18:13:58 +04:00
2020-04-15 16:39:38 +03:00
menu "RDS decoders"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2012-08-14 23:23:43 +04:00
config VIDEO_SAA6588
tristate "SAA6588 Radio Chip RDS decoder support"
depends on VIDEO_V4L2 && I2C
help
Support for this Radio Data System (RDS) decoder. This allows
seeing radio station identification transmitted using this
standard.
To compile this driver as a module, choose M here: the
module will be called saa6588.
2020-04-15 16:39:38 +03:00
endmenu
2012-08-14 23:23:43 +04:00
2020-04-15 16:39:38 +03:00
menu "Video decoders"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2012-08-14 23:23:43 +04:00
config VIDEO_ADV7180
tristate "Analog Devices ADV7180 decoder"
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 17:36:56 +03:00
depends on GPIOLIB && VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Analog Devices ADV7180 video decoder.
To compile this driver as a module, choose M here: the
module will be called adv7180.
config VIDEO_ADV7183
tristate "Analog Devices ADV7183 decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
V4l2 subdevice driver for the Analog Devices
ADV7183 video decoder.
To compile this driver as a module, choose M here: the
module will be called adv7183.
2017-07-06 14:01:16 +03:00
config VIDEO_ADV748X
tristate "Analog Devices ADV748x decoder"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
2017-07-06 14:01:16 +03:00
depends on OF
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 17:36:56 +03:00
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2017-07-06 14:01:16 +03:00
select REGMAP_I2C
2019-03-05 16:23:13 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2017-07-06 14:01:16 +03:00
V4L2 subdevice driver for the Analog Devices
ADV7481 and ADV7482 HDMI/Analog video decoders.
To compile this driver as a module, choose M here: the
module will be called adv748x.
2012-07-18 12:45:16 +04:00
config VIDEO_ADV7604
tristate "Analog Devices ADV7604 decoder"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
2015-06-29 16:45:56 +03:00
depends on GPIOLIB || 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 17:36:56 +03:00
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2020-02-26 17:34:05 +03:00
select REGMAP_I2C
2015-06-07 13:32:33 +03:00
select HDMI
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2012-07-18 12:45:16 +04:00
Support for the Analog Devices ADV7604 video decoder.
This is a Analog Devices Component/Graphics Digitizer
with 4:1 Multiplexed HDMI Receiver.
To compile this driver as a module, choose M here: the
module will be called adv7604.
2015-09-07 14:12:57 +03:00
config VIDEO_ADV7604_CEC
bool "Enable Analog Devices ADV7604 CEC support"
2017-05-28 11:48:37 +03:00
depends on VIDEO_ADV7604
select CEC_CORE
2019-03-20 13:39:44 +03:00
help
2015-09-07 14:12:57 +03:00
When selected the adv7604 will support the optional
HDMI CEC feature.
2013-08-22 13:14:22 +04:00
config VIDEO_ADV7842
tristate "Analog Devices ADV7842 decoder"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2014-12-19 15:14:23 +03:00
select HDMI
2019-03-20 13:39:44 +03:00
help
2013-08-22 13:14:22 +04:00
Support for the Analog Devices ADV7842 video decoder.
This is a Analog Devices Component/Graphics/SD Digitizer
with 2:1 Multiplexed HDMI Receiver.
To compile this driver as a module, choose M here: the
module will be called adv7842.
2015-09-07 14:13:26 +03:00
config VIDEO_ADV7842_CEC
bool "Enable Analog Devices ADV7842 CEC support"
2017-05-28 11:48:37 +03:00
depends on VIDEO_ADV7842
select CEC_CORE
2019-03-20 13:39:44 +03:00
help
2015-09-07 14:13:26 +03:00
When selected the adv7842 will support the optional
HDMI CEC feature.
2012-08-14 23:23:43 +04:00
config VIDEO_BT819
tristate "BT819A VideoStream decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for BT819A video decoder.
To compile this driver as a module, choose M here: the
module will be called bt819.
config VIDEO_BT856
tristate "BT856 VideoStream decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for BT856 video decoder.
To compile this driver as a module, choose M here: the
module will be called bt856.
config VIDEO_BT866
tristate "BT866 VideoStream decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for BT866 video decoder.
To compile this driver as a module, choose M here: the
module will be called bt866.
config VIDEO_KS0127
tristate "KS0127 video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for KS0127 video decoder.
This chip is used on AverMedia AVS6EYES Zoran-based MJPEG
cards.
To compile this driver as a module, choose M here: the
module will be called ks0127.
2013-05-29 21:52:28 +04:00
config VIDEO_ML86V7667
tristate "OKI ML86V7667 video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2013-05-29 21:52:28 +04:00
Support for the OKI Semiconductor ML86V7667 video decoder.
To compile this driver as a module, choose M here: the
module will be called ml86v7667.
2012-08-14 23:23:43 +04:00
config VIDEO_SAA7110
tristate "Philips SAA7110 video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Philips SAA7110 video decoders.
To compile this driver as a module, choose M here: the
module will be called saa7110.
config VIDEO_SAA711X
tristate "Philips SAA7111/3/4/5 video decoders"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Philips SAA7111/3/4/5 video decoders.
To compile this driver as a module, choose M here: the
module will be called saa7115.
2015-07-09 11:45:47 +03:00
config VIDEO_TC358743
tristate "Toshiba TC358743 decoder"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2015-08-19 09:27:27 +03:00
select HDMI
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2015-07-09 11:45:47 +03:00
Support for the Toshiba TC358743 HDMI to MIPI CSI-2 bridge.
To compile this driver as a module, choose M here: the
module will be called tc358743.
2017-08-31 11:12:55 +03:00
config VIDEO_TC358743_CEC
bool "Enable Toshiba TC358743 CEC support"
depends on VIDEO_TC358743
select CEC_CORE
2019-03-20 13:39:44 +03:00
help
2017-08-31 11:12:55 +03:00
When selected the tc358743 will support the optional
HDMI CEC feature.
2012-08-14 23:23:43 +04:00
config VIDEO_TVP514X
tristate "Texas Instruments TVP514x video decoder"
depends on VIDEO_V4L2 && I2C
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the TI TVP5146/47
2012-08-14 23:23:43 +04:00
decoder. It is currently working with the TI OMAP3 camera
controller.
To compile this driver as a module, choose M here: the
module will be called tvp514x.
config VIDEO_TVP5150
tristate "Texas Instruments TVP5150 video decoder"
depends on VIDEO_V4L2 && I2C
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2020-02-26 17:34:05 +03:00
select REGMAP_I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Texas Instruments TVP5150 video decoder.
To compile this driver as a module, choose M here: the
module will be called tvp5150.
config VIDEO_TVP7002
tristate "Texas Instruments TVP7002 video decoder"
depends on VIDEO_V4L2 && I2C
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Texas Instruments TVP7002 video decoder.
To compile this driver as a module, choose M here: the
module will be called tvp7002.
2013-03-09 15:06:07 +04:00
config VIDEO_TW2804
tristate "Techwell TW2804 multiple video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2013-03-09 15:06:07 +04:00
Support for the Techwell tw2804 multiple video decoder.
To compile this driver as a module, choose M here: the
module will be called tw2804.
2013-03-18 11:10:56 +04:00
config VIDEO_TW9903
tristate "Techwell TW9903 video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2013-03-09 15:06:07 +04:00
Support for the Techwell tw9903 multi-standard video decoder
2013-03-18 11:10:56 +04:00
with high quality down scaler.
To compile this driver as a module, choose M here: the
module will be called tw9903.
2013-03-17 16:26:40 +04:00
config VIDEO_TW9906
tristate "Techwell TW9906 video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2013-03-17 16:26:40 +04:00
Support for the Techwell tw9906 enhanced multi-standard comb filter
video decoder with YCbCr input support.
To compile this driver as a module, choose M here: the
module will be called tw9906.
2018-02-21 20:48:03 +03:00
config VIDEO_TW9910
tristate "Techwell TW9910 video decoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2018-02-21 20:48:03 +03:00
Support for Techwell TW9910 NTSC/PAL/SECAM video decoder.
To compile this driver as a module, choose M here: the
module will be called tw9910.
2012-08-14 23:23:43 +04:00
config VIDEO_VPX3220
tristate "vpx3220a, vpx3216b & vpx3214c video decoders"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for VPX322x video decoders.
To compile this driver as a module, choose M here: the
module will be called vpx3220.
2020-06-12 17:47:11 +03:00
config VIDEO_MAX9286
tristate "Maxim MAX9286 GMSL deserializer support"
depends on I2C && I2C_MUX
2020-08-03 12:07:06 +03:00
depends on OF_GPIO
2020-06-12 17:47:11 +03:00
select V4L2_FWNODE
select VIDEO_V4L2_SUBDEV_API
select MEDIA_CONTROLLER
help
This driver supports the Maxim MAX9286 GMSL deserializer.
To compile this driver as a module, choose M here: the
module will be called max9286.
2012-08-14 23:23:43 +04:00
comment "Video and audio decoders"
config VIDEO_SAA717X
tristate "Philips SAA7171/3/4 audio/video decoders"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Philips SAA7171/3/4 audio/video decoders.
To compile this driver as a module, choose M here: the
module will be called saa717x.
source "drivers/media/i2c/cx25840/Kconfig"
2020-04-15 16:39:38 +03:00
endmenu
menu "Video encoders"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2012-08-14 23:23:43 +04:00
config VIDEO_SAA7127
tristate "Philips SAA7127/9 digital video encoders"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Philips SAA7127/9 digital video encoders.
To compile this driver as a module, choose M here: the
module will be called saa7127.
config VIDEO_SAA7185
tristate "Philips SAA7185 video encoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Philips SAA7185 video encoder.
To compile this driver as a module, choose M here: the
module will be called saa7185.
config VIDEO_ADV7170
tristate "Analog Devices ADV7170 video encoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Analog Devices ADV7170 video encoder driver
To compile this driver as a module, choose M here: the
module will be called adv7170.
config VIDEO_ADV7175
tristate "Analog Devices ADV7175 video encoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
Support for the Analog Devices ADV7175 video encoder driver
To compile this driver as a module, choose M here: the
module will be called adv7175.
config VIDEO_ADV7343
tristate "ADV7343 video encoder"
depends on I2C
help
Support for Analog Devices I2C bus based ADV7343 encoder.
To compile this driver as a module, choose M here: the
module will be called adv7343.
config VIDEO_ADV7393
tristate "ADV7393 video encoder"
depends on I2C
help
Support for Analog Devices I2C bus based ADV7393 encoder.
To compile this driver as a module, choose M here: the
module will be called adv7393.
2013-08-23 16:12:36 +04:00
config VIDEO_ADV7511
tristate "Analog Devices ADV7511 encoder"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
2019-06-12 11:15:43 +03:00
depends on DRM_I2C_ADV7511=n || 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 17:36:56 +03:00
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2015-06-07 13:32:32 +03:00
select HDMI
2019-03-20 13:39:44 +03:00
help
2013-08-23 16:12:36 +04:00
Support for the Analog Devices ADV7511 video encoder.
This is a Analog Devices HDMI transmitter.
To compile this driver as a module, choose M here: the
module will be called adv7511.
2015-06-29 10:55:35 +03:00
config VIDEO_ADV7511_CEC
bool "Enable Analog Devices ADV7511 CEC support"
2017-05-28 11:48:37 +03:00
depends on VIDEO_ADV7511
select CEC_CORE
2019-03-20 13:39:44 +03:00
help
2015-06-29 10:55:35 +03:00
When selected the adv7511 will support the optional
HDMI CEC feature.
2012-07-18 12:46:46 +04:00
config VIDEO_AD9389B
tristate "Analog Devices AD9389B encoder"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2012-07-18 12:46:46 +04:00
Support for the Analog Devices AD9389B video encoder.
This is a Analog Devices HDMI transmitter.
To compile this driver as a module, choose M here: the
module will be called ad9389b.
2012-08-14 23:23:43 +04:00
config VIDEO_AK881X
tristate "AK8813/AK8814 video encoders"
depends on I2C
help
Video output driver for AKM AK8813 and AK8814 TV encoders
2013-06-03 20:26:17 +04:00
config VIDEO_THS8200
tristate "Texas Instruments THS8200 video encoder"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2013-06-03 20:26:17 +04:00
Support for the Texas Instruments THS8200 video encoder.
To compile this driver as a module, choose M here: the
module will be called ths8200.
2020-04-15 16:39:38 +03:00
endmenu
2013-06-03 20:26:17 +04:00
2020-04-15 16:39:38 +03:00
menu "Video improvement chips"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2012-08-14 23:23:43 +04:00
2020-03-25 17:56:15 +03:00
config VIDEO_UPD64031A
tristate "NEC Electronics uPD64031A Ghost Reduction"
depends on VIDEO_V4L2 && I2C
help
Support for the NEC Electronics uPD64031A Ghost Reduction
video chip. It is most often found in NTSC TV cards made for
Japan and is used to reduce the 'ghosting' effect that can
be present in analog TV broadcasts.
2012-08-14 23:23:43 +04:00
2020-03-25 17:56:15 +03:00
To compile this driver as a module, choose M here: the
module will be called upd64031a.
config VIDEO_UPD64083
tristate "NEC Electronics uPD64083 3-Dimensional Y/C separation"
depends on VIDEO_V4L2 && I2C
help
Support for the NEC Electronics uPD64083 3-Dimensional Y/C
separation video chip. It is used to improve the quality of
the colors of a composite signal.
To compile this driver as a module, choose M here: the
module will be called upd64083.
2020-04-15 16:39:38 +03:00
endmenu
2020-03-25 17:56:15 +03:00
2020-04-15 16:39:38 +03:00
menu "Audio/Video compression chips"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2020-03-25 17:56:15 +03:00
config VIDEO_SAA6752HS
tristate "Philips SAA6752HS MPEG-2 Audio/Video Encoder"
depends on VIDEO_V4L2 && I2C
select CRC32
help
Support for the Philips SAA6752HS MPEG-2 video and MPEG-audio/AC-3
audio encoder with multiplexer.
To compile this driver as a module, choose M here: the
module will be called saa6752hs.
2020-04-15 16:39:38 +03:00
endmenu
menu "SDR tuner chips"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2020-03-25 17:56:15 +03:00
config SDR_MAX2175
tristate "Maxim 2175 RF to Bits tuner"
depends on VIDEO_V4L2 && MEDIA_SDR_SUPPORT && I2C
select REGMAP_I2C
help
Support for Maxim 2175 tuner. It is an advanced analog/digital
radio receiver with RF-to-Bits front-end designed for SDR solutions.
To compile this driver as a module, choose M here; the
module will be called max2175.
2020-04-15 16:39:38 +03:00
endmenu
menu "Miscellaneous helper chips"
visible if !MEDIA_HIDE_ANCILLARY_SUBDRV
2020-03-25 17:56:15 +03:00
config VIDEO_THS7303
tristate "THS7303/53 Video Amplifier"
depends on VIDEO_V4L2 && I2C
help
Support for TI THS7303/53 video amplifier
To compile this driver as a module, choose M here: the
module will be called ths7303.
config VIDEO_M52790
tristate "Mitsubishi M52790 A/V switch"
depends on VIDEO_V4L2 && I2C
help
Support for the Mitsubishi M52790 A/V switch.
To compile this driver as a module, choose M here: the
module will be called m52790.
config VIDEO_I2C
tristate "I2C transport video support"
depends on VIDEO_V4L2 && I2C
select VIDEOBUF2_VMALLOC
imply HWMON
help
Enable the I2C transport video support which supports the
following:
* Panasonic AMG88xx Grid-Eye Sensors
* Melexis MLX90640 Thermal Cameras
To compile this driver as a module, choose M here: the
module will be called video-i2c
config VIDEO_ST_MIPID02
tristate "STMicroelectronics MIPID02 CSI-2 to PARALLEL bridge"
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
help
Support for STMicroelectronics MIPID02 CSI-2 to PARALLEL bridge.
It is used to allow usage of CSI-2 sensor with PARALLEL port
controller.
To compile this driver as a module, choose M here: the
module will be called st-mipid02.
endmenu
2012-08-14 23:23:43 +04:00
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 17:36:56 +03:00
#
2020-04-15 16:39:38 +03:00
# V4L2 I2C drivers that are related with Camera support
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 17:36:56 +03:00
#
2020-04-15 16:39:38 +03:00
menu "Camera sensor devices"
visible if MEDIA_CAMERA_SUPPORT
2020-03-25 17:56:15 +03:00
config VIDEO_APTINA_PLL
tristate
2020-05-28 00:59:40 +03:00
config VIDEO_CCS_PLL
2020-03-25 17:56:15 +03:00
tristate
2019-11-01 13:44:31 +03:00
config VIDEO_HI556
tristate "Hynix Hi-556 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-11-01 13:44:31 +03:00
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the Hynix
Hi-556 camera.
To compile this driver as a module, choose M here: the
module will be called hi556.
2018-10-06 01:58:31 +03:00
config VIDEO_IMX214
tristate "Sony IMX214 sensor support"
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 17:36:56 +03:00
depends on GPIOLIB && I2C && VIDEO_V4L2
2020-06-22 19:43:52 +03:00
select V4L2_FWNODE
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 17:36:56 +03:00
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2020-02-26 17:34:05 +03:00
select REGMAP_I2C
2018-10-06 01:58:31 +03:00
help
This is a Video4Linux2 sensor driver for the Sony
IMX214 camera.
To compile this driver as a module, choose M here: the
module will be called imx214.
2020-01-20 11:15:58 +03:00
config VIDEO_IMX219
tristate "Sony IMX219 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2020-01-20 11:15:58 +03:00
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the Sony
IMX219 camera.
To compile this driver as a module, choose M here: the
module will be called imx219.
2018-05-02 18:46:08 +03:00
config VIDEO_IMX258
tristate "Sony IMX258 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Sony
2018-05-02 18:46:08 +03:00
IMX258 camera.
To compile this driver as a module, choose M here: the
module will be called imx258.
2017-10-05 03:06:21 +03:00
config VIDEO_IMX274
tristate "Sony IMX274 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2018-11-27 11:34:45 +03:00
select REGMAP_I2C
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for the Sony IMX274
2017-10-05 03:06:21 +03:00
CMOS image sensor.
2019-10-04 19:05:25 +03:00
config VIDEO_IMX290
tristate "Sony IMX290 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2020-02-26 17:34:05 +03:00
select REGMAP_I2C
2019-10-04 19:05:25 +03:00
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the Sony
IMX290 camera sensor.
To compile this driver as a module, choose M here: the
module will be called imx290.
2018-09-26 05:42:18 +03:00
config VIDEO_IMX319
tristate "Sony IMX319 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2018-09-26 05:42:18 +03:00
help
This is a Video4Linux2 sensor driver for the Sony
IMX319 camera.
To compile this driver as a module, choose M here: the
module will be called imx319.
2021-02-03 16:54:41 +03:00
config VIDEO_IMX334
tristate "Sony IMX334 sensor support"
depends on OF_GPIO
depends on I2C && VIDEO_V4L2
select VIDEO_V4L2_SUBDEV_API
select MEDIA_CONTROLLER
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the Sony
IMX334 camera.
To compile this driver as a module, choose M here: the
module will be called imx334.
media: add imx355 camera sensor driver
Add a v4l2 sub-device driver for the Sony imx355 image sensor.
This is a camera sensor using the i2c bus for control and the
csi-2 bus for data.
This driver supports following features:
- manual exposure and analog/digital gain control support
- vblank/hblank control support
- 4 test patterns control support
- vflip/hflip control support (will impact the output bayer order)
- support following resolutions:
- 3268x2448, 3264x2448, 3280x2464 @ 30fps
- 1940x1096, 1936x1096, 1924x1080, 1920x1080 @ 60fps
- 1640x1232, 1640x922, 1300x736, 1296x736,
1284x720, 1280x720 820x616 @ 120fps
- support 4 bayer orders output (via change v/hflip)
- SRGGB10(default), SGRBG10, SGBRG10, SBGGR10
[Sakari Ailus: Use do_div() for dividing 64-bit numbers, fix fwnode if usage]
Cc: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Tianshu Qiu <tian.shu.qiu@intel.com>
Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
2018-09-29 13:03:54 +03:00
config VIDEO_IMX355
tristate "Sony IMX355 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
media: add imx355 camera sensor driver
Add a v4l2 sub-device driver for the Sony imx355 image sensor.
This is a camera sensor using the i2c bus for control and the
csi-2 bus for data.
This driver supports following features:
- manual exposure and analog/digital gain control support
- vblank/hblank control support
- 4 test patterns control support
- vflip/hflip control support (will impact the output bayer order)
- support following resolutions:
- 3268x2448, 3264x2448, 3280x2464 @ 30fps
- 1940x1096, 1936x1096, 1924x1080, 1920x1080 @ 60fps
- 1640x1232, 1640x922, 1300x736, 1296x736,
1284x720, 1280x720 820x616 @ 120fps
- support 4 bayer orders output (via change v/hflip)
- SRGGB10(default), SGRBG10, SGBRG10, SBGGR10
[Sakari Ailus: Use do_div() for dividing 64-bit numbers, fix fwnode if usage]
Cc: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Tianshu Qiu <tian.shu.qiu@intel.com>
Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
2018-09-29 13:03:54 +03:00
help
This is a Video4Linux2 sensor driver for the Sony
IMX355 camera.
To compile this driver as a module, choose M here: the
module will be called imx355.
2020-11-25 17:17:56 +03:00
config VIDEO_OV02A10
tristate "OmniVision OV02A10 sensor support"
depends on VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the OmniVision
OV02A10 camera.
To compile this driver as a module, choose M here: the
module will be called ov02a10.
2016-11-22 19:44:37 +03:00
config VIDEO_OV2640
tristate "OmniVision OV2640 sensor support"
2017-04-19 14:43:49 +03:00
depends on VIDEO_V4L2 && I2C
2016-11-22 19:44:37 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2016-11-22 19:44:37 +03:00
OV2640 camera.
To compile this driver as a module, choose M here: the
module will be called ov2640.
2015-03-21 00:03:52 +03:00
config VIDEO_OV2659
tristate "OmniVision OV2659 sensor support"
2019-09-30 16:06:42 +03:00
depends on VIDEO_V4L2 && I2C && GPIOLIB
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2015-03-21 00:03:52 +03:00
OV2659 camera.
To compile this driver as a module, choose M here: the
module will be called ov2659.
2018-07-03 17:08:03 +03:00
config VIDEO_OV2680
tristate "OmniVision OV2680 sensor support"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
2018-07-03 17:08:03 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-03 17:08:03 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
OV2680 camera.
To compile this driver as a module, choose M here: the
module will be called ov2680.
2018-01-16 12:22:01 +03:00
config VIDEO_OV2685
tristate "OmniVision OV2685 sensor support"
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 17:36:56 +03:00
depends on VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
2018-01-16 12:22:01 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2018-01-16 12:22:01 +03:00
OV2685 camera.
To compile this driver as a module, choose M here: the
module will be called ov2685.
2020-05-11 16:41:14 +03:00
config VIDEO_OV2740
tristate "OmniVision OV2740 sensor support"
depends on VIDEO_V4L2 && I2C
2020-06-04 04:25:19 +03:00
depends on ACPI || COMPILE_TEST
2020-05-11 16:41:14 +03:00
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
2020-09-30 04:13:22 +03:00
select REGMAP_I2C
2020-05-11 16:41:14 +03:00
help
This is a Video4Linux2 sensor driver for the OmniVision
OV2740 camera.
To compile this driver as a module, choose M here: the
module will be called ov2740.
2017-06-07 21:33:56 +03:00
config VIDEO_OV5640
tristate "OmniVision OV5640 sensor support"
depends on OF
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 17:36:56 +03:00
depends on GPIOLIB && VIDEO_V4L2 && I2C
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2017-06-07 21:33:56 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Omnivision
2017-06-07 21:33:56 +03:00
OV5640 camera sensor with a MIPI CSI-2 interface.
2017-04-11 14:28:46 +03:00
config VIDEO_OV5645
tristate "OmniVision OV5645 sensor support"
depends on OF
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2017-04-11 14:28:46 +03:00
OV5645 camera.
To compile this driver as a module, choose M here: the
module will be called ov5645.
2017-03-22 15:30:27 +03:00
config VIDEO_OV5647
tristate "OmniVision OV5647 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2017-03-22 15:30:27 +03:00
OV5647 camera.
To compile this driver as a module, choose M here: the
module will be called ov5647.
2020-12-31 17:23:57 +03:00
config VIDEO_OV5648
tristate "OmniVision OV5648 sensor support"
depends on I2C && PM && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the OmniVision
OV5648 camera.
To compile this driver as a module, choose M here: the
module will be called ov5648.
2017-06-16 22:45:33 +03:00
config VIDEO_OV6650
tristate "OmniVision OV6650 sensor support"
depends on I2C && VIDEO_V4L2
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2017-06-16 22:45:33 +03:00
OV6650 camera.
To compile this driver as a module, choose M here: the
module will be called ov6650.
2017-07-14 04:51:27 +03:00
config VIDEO_OV5670
tristate "OmniVision OV5670 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2017-07-14 04:51:27 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2017-07-14 04:51:27 +03:00
OV5670 camera.
To compile this driver as a module, choose M here: the
module will be called ov5670.
2019-08-07 13:07:56 +03:00
config VIDEO_OV5675
tristate "OmniVision OV5675 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-08-07 13:07:56 +03:00
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the OmniVision
OV5675 camera.
To compile this driver as a module, choose M here: the
module will be called ov5675.
2018-01-16 12:21:59 +03:00
config VIDEO_OV5695
tristate "OmniVision OV5695 sensor support"
depends on I2C && VIDEO_V4L2
2019-10-06 10:38:38 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2018-01-16 12:21:59 +03:00
OV5695 camera.
To compile this driver as a module, choose M here: the
module will be called ov5695.
2018-04-25 19:20:46 +03:00
config VIDEO_OV7251
tristate "OmniVision OV7251 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2018-04-25 19:20:46 +03:00
select V4L2_FWNODE
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2018-04-25 19:20:46 +03:00
OV7251 camera.
To compile this driver as a module, choose M here: the
module will be called ov7251.
2018-02-21 20:48:00 +03:00
config VIDEO_OV772X
tristate "OmniVision OV772x sensor support"
depends on I2C && VIDEO_V4L2
2018-07-16 18:47:49 +03:00
select REGMAP_SCCB
2021-01-20 12:01:48 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2018-02-21 20:48:00 +03:00
OV772x camera.
To compile this driver as a module, choose M here: the
module will be called ov772x.
2013-03-09 14:09:18 +04:00
config VIDEO_OV7640
tristate "OmniVision OV7640 sensor support"
depends on I2C && VIDEO_V4L2
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2013-03-09 14:09:18 +04:00
OV7640 camera.
To compile this driver as a module, choose M here: the
module will be called ov7640.
2012-08-14 23:23:43 +04:00
config VIDEO_OV7670
tristate "OmniVision OV7670 sensor support"
depends on I2C && VIDEO_V4L2
2018-01-24 12:30:50 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2012-08-14 23:23:43 +04:00
OV7670 VGA camera. It currently only works with the M88ALP01
controller.
2017-12-11 04:31:46 +03:00
config VIDEO_OV7740
tristate "OmniVision OV7740 sensor support"
depends on I2C && VIDEO_V4L2
2020-08-06 18:48:27 +03:00
select REGMAP_SCCB
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2017-12-11 04:31:46 +03:00
OV7740 VGA camera sensor.
2019-01-15 11:30:29 +03:00
config VIDEO_OV8856
tristate "OmniVision OV8856 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-01-15 11:30:29 +03:00
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the OmniVision
OV8856 camera sensor.
To compile this driver as a module, choose M here: the
module will be called ov8856.
2020-12-31 17:27:01 +03:00
config VIDEO_OV8865
tristate "OmniVision OV8865 sensor support"
depends on I2C && PM && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for OmniVision
OV8865 camera sensor.
To compile this driver as a module, choose M here: the
module will be called ov8865.
2018-12-13 18:39:12 +03:00
config VIDEO_OV9640
tristate "OmniVision OV9640 sensor support"
depends on I2C && VIDEO_V4L2
help
This is a Video4Linux2 sensor driver for the OmniVision
OV9640 camera sensor.
[media] V4L: Add driver for OV9650/52 image sensors
This patch adds V4L2 sub-device driver for OV9650/OV9652 image sensors.
The driver exposes following V4L2 controls:
- auto/manual exposure,
- auto/manual white balance,
- auto/manual gain,
- brightness, saturation, sharpness,
- horizontal/vertical flip,
- color bar test pattern,
- banding filter (power line frequency).
Frame rate can be configured with g/s_frame_interval pad level ops.
Supported resolution are only: SXGA, VGA, QVGA.
Signed-off-by: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-12-26 22:50:03 +04:00
config VIDEO_OV9650
tristate "OmniVision OV9650/OV9652 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2018-07-16 18:47:50 +03:00
select REGMAP_SCCB
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for the Omnivision
[media] V4L: Add driver for OV9650/52 image sensors
This patch adds V4L2 sub-device driver for OV9650/OV9652 image sensors.
The driver exposes following V4L2 controls:
- auto/manual exposure,
- auto/manual white balance,
- auto/manual gain,
- brightness, saturation, sharpness,
- horizontal/vertical flip,
- color bar test pattern,
- banding filter (power line frequency).
Frame rate can be configured with g/s_frame_interval pad level ops.
Supported resolution are only: SXGA, VGA, QVGA.
Signed-off-by: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-12-26 22:50:03 +04:00
OV9650 and OV9652 camera sensors.
2020-10-29 05:59:01 +03:00
config VIDEO_OV9734
tristate "OmniVision OV9734 sensor support"
depends on VIDEO_V4L2 && I2C
depends on ACPI || COMPILE_TEST
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
help
This is a Video4Linux2 sensor driver for the OmniVision
OV9734 camera.
To compile this driver as a module, choose M here: the
module's name is ov9734.
2017-06-14 01:06:16 +03:00
config VIDEO_OV13858
tristate "OmniVision OV13858 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2017-11-06 01:51:00 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the OmniVision
2017-06-14 01:06:16 +03:00
OV13858 camera.
2012-08-14 23:23:43 +04:00
config VIDEO_VS6624
tristate "ST VS6624 sensor support"
depends on VIDEO_V4L2 && I2C
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the ST VS6624
2012-08-14 23:23:43 +04:00
camera.
To compile this driver as a module, choose M here: the
module will be called vs6624.
2019-01-08 17:51:38 +03:00
config VIDEO_MT9M001
tristate "mt9m001 support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-01-08 17:51:38 +03:00
help
This driver supports MT9M001 cameras from Micron, monochrome
and colour models.
2012-08-14 23:23:43 +04:00
config VIDEO_MT9M032
tristate "MT9M032 camera sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2012-08-14 23:23:43 +04:00
select VIDEO_APTINA_PLL
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
This driver supports MT9M032 camera sensors from Aptina, monochrome
models only.
2016-09-06 12:04:13 +03:00
config VIDEO_MT9M111
tristate "mt9m111, mt9m112 and mt9m131 support"
depends on I2C && VIDEO_V4L2
2018-11-27 13:02:53 +03:00
select V4L2_FWNODE
2016-09-06 12:04:13 +03:00
help
This driver supports MT9M111, MT9M112 and MT9M131 cameras from
Micron/Aptina
2012-08-14 23:23:43 +04:00
config VIDEO_MT9P031
tristate "Aptina MT9P031 support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2012-08-14 23:23:43 +04:00
select VIDEO_APTINA_PLL
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Aptina
2012-08-14 23:23:43 +04:00
(Micron) mt9p031 5 Mpixel camera.
config VIDEO_MT9T001
tristate "Aptina MT9T001 support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Aptina
2012-08-14 23:23:43 +04:00
(Micron) mt0t001 3 Mpixel camera.
2018-03-12 16:43:03 +03:00
config VIDEO_MT9T112
tristate "Aptina MT9T111/MT9T112 support"
depends on I2C && VIDEO_V4L2
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Aptina
2018-03-12 16:43:03 +03:00
(Micron) MT9T111 and MT9T112 3 Mpixel camera.
To compile this driver as a module, choose M here: the
module will be called mt9t112.
2012-08-14 23:23:43 +04:00
config VIDEO_MT9V011
tristate "Micron mt9v011 sensor support"
depends on I2C && VIDEO_V4L2
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Micron
2012-08-14 23:23:43 +04:00
mt0v011 1.3 Mpixel camera. It currently only works with the
em28xx driver.
config VIDEO_MT9V032
tristate "Micron MT9V032 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2014-06-04 20:57:03 +04:00
select REGMAP_I2C
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a Video4Linux2 sensor driver for the Micron
2012-08-14 23:23:43 +04:00
MT9V032 752x480 CMOS sensor.
2018-07-25 16:44:31 +03:00
config VIDEO_MT9V111
tristate "Aptina MT9V111 sensor support"
depends on I2C && VIDEO_V4L2
help
This is a Video4Linux2 sensor driver for the Aptina/Micron
MT9V111 sensor.
To compile this driver as a module, choose M here: the
module will be called mt9v111.
2012-08-14 23:23:43 +04:00
config VIDEO_SR030PC30
tristate "Siliconfile SR030PC30 sensor support"
depends on I2C && VIDEO_V4L2
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
This driver supports SR030PC30 VGA camera from Siliconfile
config VIDEO_NOON010PC30
tristate "Siliconfile NOON010PC30 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
This driver supports NOON010PC30 CIF camera from Siliconfile
source "drivers/media/i2c/m5mols/Kconfig"
2021-02-09 14:09:21 +03:00
config VIDEO_MAX9271_LIB
tristate
2020-06-12 17:47:13 +03:00
config VIDEO_RDACM20
tristate "IMI RDACM20 camera support"
depends on I2C
select V4L2_FWNODE
select VIDEO_V4L2_SUBDEV_API
select MEDIA_CONTROLLER
2021-02-09 14:09:21 +03:00
select VIDEO_MAX9271_LIB
2020-06-12 17:47:13 +03:00
help
This driver supports the IMI RDACM20 GMSL camera, used in
ADAS systems.
This camera should be used in conjunction with a GMSL
deserialiser such as the MAX9286.
2021-01-14 20:04:25 +03:00
config VIDEO_RDACM21
tristate "IMI RDACM21 camera support"
depends on I2C
select V4L2_FWNODE
select VIDEO_V4L2_SUBDEV_API
select MEDIA_CONTROLLER
2021-02-09 14:09:21 +03:00
select VIDEO_MAX9271_LIB
2021-01-14 20:04:25 +03:00
help
This driver supports the IMI RDACM21 GMSL camera, used in
ADAS systems.
This camera should be used in conjunction with a GMSL
deserialiser such as the MAX9286.
2018-05-28 19:37:08 +03:00
config VIDEO_RJ54N1
tristate "Sharp RJ54N1CB0C sensor support"
depends on I2C && VIDEO_V4L2
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for Sharp RJ54N1CB0C CMOS image
2018-05-28 19:37:08 +03:00
sensor.
To compile this driver as a module, choose M here: the
module will be called rj54n1.
2012-08-14 23:23:43 +04:00
config VIDEO_S5K6AA
tristate "Samsung S5K6AAFX sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for Samsung S5K6AA(FX) 1.3M
2012-08-14 23:23:43 +04:00
camera sensor with an embedded SoC image signal processor.
2013-08-09 22:56:00 +04:00
config VIDEO_S5K6A3
tristate "Samsung S5K6A3 sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for Samsung S5K6A3 raw
2013-08-09 22:56:00 +04:00
camera sensor.
2012-09-13 14:02:14 +04:00
config VIDEO_S5K4ECGX
2018-01-04 14:47:28 +03:00
tristate "Samsung S5K4ECGX sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2016-12-09 14:41:29 +03:00
select CRC32
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for Samsung S5K4ECGX 5M
2018-01-04 14:47:28 +03:00
camera sensor with an embedded SoC image signal processor.
2012-09-13 14:02:14 +04:00
2013-12-05 15:38:39 +04:00
config VIDEO_S5K5BAF
tristate "Samsung S5K5BAF sensor support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for Samsung S5K5BAF 2M
2013-12-05 15:38:39 +04:00
camera sensor with an embedded SoC image signal processor.
2020-02-11 21:05:57 +03:00
source "drivers/media/i2c/ccs/Kconfig"
2016-12-22 13:01:04 +03:00
source "drivers/media/i2c/et8ek8/Kconfig"
2012-08-14 23:23:43 +04:00
2012-11-22 18:39:18 +04:00
config VIDEO_S5C73M3
tristate "Samsung S5C73M3 sensor support"
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 17:36:56 +03:00
depends on I2C && SPI && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2016-08-27 02:17:25 +03:00
select V4L2_FWNODE
2019-03-20 13:39:44 +03:00
help
2018-07-16 18:20:33 +03:00
This is a V4L2 sensor driver for Samsung S5C73M3
2013-04-25 17:46:38 +04:00
8 Mpixel camera.
2012-11-22 18:39:18 +04:00
2020-04-15 16:39:38 +03:00
endmenu
menu "Lens drivers"
visible if MEDIA_CAMERA_SUPPORT
2019-03-18 18:21:13 +03:00
config VIDEO_AD5820
tristate "AD5820 lens voice coil support"
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 17:36:56 +03:00
depends on GPIOLIB && I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
2019-03-20 13:39:44 +03:00
help
2019-03-18 18:21:13 +03:00
This is a driver for the AD5820 camera lens voice coil.
It is used for example in Nokia N900 (RX-51).
config VIDEO_AK7375
tristate "AK7375 lens voice coil support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-18 18:21:13 +03:00
help
This is a driver for the AK7375 camera lens voice coil.
AK7375 is a 12 bit DAC with 120mA output current sink
capability. This is designed for linear control of
voice coil motors, controlled via I2C serial interface.
config VIDEO_DW9714
tristate "DW9714 lens voice coil support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2019-03-18 18:21:13 +03:00
This is a driver for the DW9714 camera lens voice coil.
DW9714 is a 10 bit DAC with 120mA output current sink
capability. This is designed for linear control of
voice coil motors, controlled via I2C serial interface.
2020-06-30 09:22:11 +03:00
config VIDEO_DW9768
tristate "DW9768 lens voice coil support"
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
select V4L2_FWNODE
help
This is a driver for the DW9768 camera lens voice coil.
DW9768 is a 10 bit DAC with 100mA output current sink
capability. This is designed for linear control of
voice coil motors, controlled via I2C serial interface.
2019-03-18 18:21:13 +03:00
config VIDEO_DW9807_VCM
tristate "DW9807 lens voice coil support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
select VIDEO_V4L2_SUBDEV_API
2019-03-20 13:39:44 +03:00
help
2019-03-18 18:21:13 +03:00
This is a driver for the DW9807 camera lens voice coil.
DW9807 is a 10 bit DAC with 100mA output current sink
capability. This is designed for linear control of
voice coil motors, controlled via I2C serial interface.
2020-04-15 16:39:38 +03:00
endmenu
2019-09-23 11:51:24 +03:00
2020-04-15 16:39:38 +03:00
menu "Flash devices"
visible if MEDIA_CAMERA_SUPPORT
2012-08-14 23:23:43 +04:00
config VIDEO_ADP1653
tristate "ADP1653 flash support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
2019-03-20 13:39:44 +03:00
help
2012-08-14 23:23:43 +04:00
This is a driver for the ADP1653 flash controller. It is used for
example in Nokia N900.
2013-10-16 11:12:19 +04:00
config VIDEO_LM3560
tristate "LM3560 dual flash driver support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
2013-10-16 11:12:19 +04:00
select REGMAP_I2C
2019-03-20 13:39:44 +03:00
help
2013-10-16 11:12:19 +04:00
This is a driver for the lm3560 dual flash controllers. It controls
flash, torch LEDs.
2014-03-03 13:52:10 +04:00
config VIDEO_LM3646
tristate "LM3646 dual flash driver support"
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 17:36:56 +03:00
depends on I2C && VIDEO_V4L2
select MEDIA_CONTROLLER
2014-03-03 13:52:10 +04:00
select REGMAP_I2C
2019-03-20 13:39:44 +03:00
help
2014-03-03 13:52:10 +04:00
This is a driver for the lm3646 dual flash controllers. It controls
flash, torch LEDs.
2020-04-15 16:39:38 +03:00
endmenu
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 17:36:56 +03:00
endif # VIDEO_V4L2
