2019-05-19 13:07:45 +01:00
# SPDX-License-Identifier: GPL-2.0-only
2005-04-16 15:20:36 -07:00
#
# Multimedia device configuration
#
2017-05-28 05:48:37 -03:00
config CEC_CORE
tristate
2017-05-28 05:58:04 -03:00
config CEC_NOTIFIER
2017-05-28 05:48:37 -03:00
bool
2017-07-11 03:30:42 -03:00
config CEC_PIN
bool
2017-07-02 15:37:58 -04:00
source "drivers/media/rc/Kconfig"
2009-05-18 22:00:34 -03:00
menuconfig MEDIA_SUPPORT
tristate "Multimedia support"
2007-05-10 15:45:57 +02:00
depends on HAS_IOMEM
2009-05-18 22:00:34 -03:00
help
2020-03-24 10:15:43 +01:00
If you want to use media devices, including Webcams, Video grabber
devices and/or TV devices, V4L2 codecs, etc, enable this option
and other options below.
2012-05-28 08:17:47 -03:00
Additional info and docs are available on the web at
2015-12-04 10:38:59 -02:00
<https://linuxtv.org>
2009-05-18 22:00:34 -03:00
2020-03-24 10:25:09 +01:00
menu "Types of devices to be supported"
depends on MEDIA_SUPPORT
2008-04-29 21:38:44 -03:00
2012-05-28 08:17:47 -03:00
#
# Multimedia support - automatically enable V4L2 and DVB core
#
config MEDIA_CAMERA_SUPPORT
2020-03-24 10:25:09 +01:00
bool "Cameras and video grabbers"
2019-03-20 06:39:44 -04:00
help
2012-05-28 08:17:47 -03:00
Enable support for webcams and video grabbers.
Say Y when you have a webcam or a video capture grabber board.
config MEDIA_ANALOG_TV_SUPPORT
2020-03-24 10:25:09 +01:00
bool "Analog TV"
2019-03-20 06:39:44 -04:00
help
2012-05-28 08:17:47 -03:00
Enable analog TV support.
media: Kconfig: better support hybrid TV devices
Right now, if one has an hybrid TV card, it has to select
both analog and digital TV support, as otherwise the needed
core support won't be selected.
Change the logic to auto-select the core support for those
drivers, as this is a way more intuitive.
It should be noticed that, as now both DVB_CORE and VIDEO_DEV
defaults depends on selecting a hybrid cards, we had to remove
the explicit dependencies there, in order to avoid circular
dependencies.
That requires some tricks:
1) the prompt should not be not visible when an hybrid card
is selected, as the user shold not change it.
2) When a media hybrid device is selected, the modular
option for DVB_CORE and VIDEO_DEV will follow the
MEDIA_SUPPORT dependency, as we can't have a core
built with "y" with a driver built as module.
Note: while here, moved two pure V4L2 PCI drivers out of the
"hybrid" part of config and consider pvrusb2 as an hybrid
device.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 08:36:36 +01:00
Say Y when you have a board with analog TV support.
2012-05-28 08:17:47 -03:00
config MEDIA_DIGITAL_TV_SUPPORT
2020-03-24 10:25:09 +01:00
bool "Digital TV"
2019-03-20 06:39:44 -04:00
help
2012-05-28 08:17:47 -03:00
Enable digital TV support.
media: Kconfig: better support hybrid TV devices
Right now, if one has an hybrid TV card, it has to select
both analog and digital TV support, as otherwise the needed
core support won't be selected.
Change the logic to auto-select the core support for those
drivers, as this is a way more intuitive.
It should be noticed that, as now both DVB_CORE and VIDEO_DEV
defaults depends on selecting a hybrid cards, we had to remove
the explicit dependencies there, in order to avoid circular
dependencies.
That requires some tricks:
1) the prompt should not be not visible when an hybrid card
is selected, as the user shold not change it.
2) When a media hybrid device is selected, the modular
option for DVB_CORE and VIDEO_DEV will follow the
MEDIA_SUPPORT dependency, as we can't have a core
built with "y" with a driver built as module.
Note: while here, moved two pure V4L2 PCI drivers out of the
"hybrid" part of config and consider pvrusb2 as an hybrid
device.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 08:36:36 +01:00
Say Y when you have a board with digital TV support.
2012-05-28 08:17:47 -03:00
config MEDIA_RADIO_SUPPORT
2020-03-24 10:25:09 +01:00
bool "AM/FM radio receivers/transmitters"
2019-03-20 06:39:44 -04:00
help
2012-05-28 08:17:47 -03:00
Enable AM/FM radio support.
Additional info and docs are available on the web at
2015-12-04 10:38:59 -02:00
<https://linuxtv.org>
2012-05-28 08:17:47 -03:00
Say Y when you have a board with radio support.
2014-07-12 21:43:12 -03:00
config MEDIA_SDR_SUPPORT
2020-03-24 10:25:09 +01:00
bool "Software defined radio"
2019-03-20 06:39:44 -04:00
help
2014-07-12 21:43:12 -03:00
Enable software defined radio support.
Say Y when you have a software defined radio device.
2016-11-02 08:25:28 -02:00
config MEDIA_CEC_SUPPORT
2020-03-24 10:25:09 +01:00
bool "HDMI CEC"
2019-03-20 06:39:44 -04:00
help
2018-05-02 19:19:30 -04:00
Enable support for HDMI CEC (Consumer Electronics Control),
which is an optional HDMI feature.
2016-11-02 08:25:28 -02:00
2018-05-02 19:19:30 -04:00
Say Y when you have an HDMI receiver, transmitter or a USB CEC
adapter that supports HDMI CEC.
2016-06-17 09:13:08 -03:00
2020-03-24 10:27:15 +01:00
config MEDIA_PLATFORM_SUPPORT
2020-03-24 10:25:09 +01:00
bool "Platform-specific devices"
2020-03-24 10:27:15 +01:00
help
Enable support for complex cameras, codecs, and other hardware
that are integrated at the CPU, GPU or on Image Signalling Processor
and don't use PCI, USB or Firewire buses.
This is found on Embedded hardware (SoC), on V4L2 codecs and
on some GPU and newer CPU chipsets.
Say Y when you want to be able so see such devices.
media: split test drivers from platform directory
When the first test device was added (vivi.c), there were just
one file. I was too lazy on that time to create a separate
directory just for it, so I kept it together with platform.
Now, we have vivid, vicodec, vim2m and vimc. Also, a new
virtual driver has been prepared to support DVB API.
So, it is time to solve this mess, by placing test stuff
on a separate directory.
It should be noticed that we also have some skeleton drivers
(for V4L and for DVB). For now, we'll keep them separate,
as they're not really test drivers, but instead, just
examples. The DVB frontend ones will likely be part of a new DVB
test driver. By that time, it should make sense to move them
here as well.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-24 10:39:43 +01:00
config MEDIA_TEST_SUPPORT
2020-03-24 10:25:09 +01:00
bool "Test drivers"
media: split test drivers from platform directory
When the first test device was added (vivi.c), there were just
one file. I was too lazy on that time to create a separate
directory just for it, so I kept it together with platform.
Now, we have vivid, vicodec, vim2m and vimc. Also, a new
virtual driver has been prepared to support DVB API.
So, it is time to solve this mess, by placing test stuff
on a separate directory.
It should be noticed that we also have some skeleton drivers
(for V4L and for DVB). For now, we'll keep them separate,
as they're not really test drivers, but instead, just
examples. The DVB frontend ones will likely be part of a new DVB
test driver. By that time, it should make sense to move them
here as well.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-24 10:39:43 +01:00
help
Those drivers should not be used on production Kernels, but
can be useful on debug ones. It enables several dummy drivers
that simulate a real hardware. Very useful to test userspace
applications and to validate if the subsystem core is doesn't
have regressions.
Say Y if you want to use some virtual test driver.
In case of doubts, say N.
2020-03-24 10:25:09 +01:00
Say Y when you have a software defined radio device.
endmenu # Types of devices to be supported
if MEDIA_SUPPORT
media: split test drivers from platform directory
When the first test device was added (vivi.c), there were just
one file. I was too lazy on that time to create a separate
directory just for it, so I kept it together with platform.
Now, we have vivid, vicodec, vim2m and vimc. Also, a new
virtual driver has been prepared to support DVB API.
So, it is time to solve this mess, by placing test stuff
on a separate directory.
It should be noticed that we also have some skeleton drivers
(for V4L and for DVB). For now, we'll keep them separate,
as they're not really test drivers, but instead, just
examples. The DVB frontend ones will likely be part of a new DVB
test driver. By that time, it should make sense to move them
here as well.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-24 10:39:43 +01:00
2020-03-24 10:14:15 +01:00
comment "Multimedia core features"
2018-12-05 12:23:54 -05:00
2008-04-29 21:38:44 -03:00
#
2012-05-28 08:17:47 -03:00
# Video4Linux support
# Only enables if one of the V4L2 types (ATV, webcam, radio) is selected
2008-04-29 21:38:44 -03:00
#
media: Kconfig: better support hybrid TV devices
Right now, if one has an hybrid TV card, it has to select
both analog and digital TV support, as otherwise the needed
core support won't be selected.
Change the logic to auto-select the core support for those
drivers, as this is a way more intuitive.
It should be noticed that, as now both DVB_CORE and VIDEO_DEV
defaults depends on selecting a hybrid cards, we had to remove
the explicit dependencies there, in order to avoid circular
dependencies.
That requires some tricks:
1) the prompt should not be not visible when an hybrid card
is selected, as the user shold not change it.
2) When a media hybrid device is selected, the modular
option for DVB_CORE and VIDEO_DEV will follow the
MEDIA_SUPPORT dependency, as we can't have a core
built with "y" with a driver built as module.
Note: while here, moved two pure V4L2 PCI drivers out of the
"hybrid" part of config and consider pvrusb2 as an hybrid
device.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 08:36:36 +01:00
comment "Video4Linux core enabled to support hybrid TV devices"
depends on MEDIA_HYBRID_USB || MEDIA_HYBRID_PCI
2005-04-16 15:20:36 -07:00
config VIDEO_DEV
2012-05-28 08:17:47 -03:00
tristate
media: Kconfig: better support hybrid TV devices
Right now, if one has an hybrid TV card, it has to select
both analog and digital TV support, as otherwise the needed
core support won't be selected.
Change the logic to auto-select the core support for those
drivers, as this is a way more intuitive.
It should be noticed that, as now both DVB_CORE and VIDEO_DEV
defaults depends on selecting a hybrid cards, we had to remove
the explicit dependencies there, in order to avoid circular
dependencies.
That requires some tricks:
1) the prompt should not be not visible when an hybrid card
is selected, as the user shold not change it.
2) When a media hybrid device is selected, the modular
option for DVB_CORE and VIDEO_DEV will follow the
MEDIA_SUPPORT dependency, as we can't have a core
built with "y" with a driver built as module.
Note: while here, moved two pure V4L2 PCI drivers out of the
"hybrid" part of config and consider pvrusb2 as an hybrid
device.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 08:36:36 +01:00
prompt "Video4Linux core" if !(MEDIA_HYBRID_USB || MEDIA_HYBRID_PCI)
2020-03-26 15:47:25 +01:00
default MEDIA_CAMERA_SUPPORT || MEDIA_ANALOG_TV_SUPPORT || MEDIA_RADIO_SUPPORT || MEDIA_SDR_SUPPORT || MEDIA_PLATFORM_SUPPORT || MEDIA_TEST_SUPPORT || MEDIA_HYBRID_USB || MEDIA_HYBRID_PCI
2005-04-16 15:20:36 -07:00
2010-05-21 06:04:24 -03:00
config VIDEO_V4L2_SUBDEV_API
2012-10-02 11:17:27 -07:00
bool "V4L2 sub-device userspace API"
depends on VIDEO_DEV && MEDIA_CONTROLLER
2019-03-20 06:39:44 -04:00
help
2010-05-21 06:04:24 -03:00
Enables the V4L2 sub-device pad-level userspace API used to configure
video format, size and frame rate between hardware blocks.
This API is mostly used by camera interfaces in embedded platforms.
2008-04-29 21:38:44 -03:00
#
# DVB Core
2012-05-28 08:17:47 -03:00
# Only enables if one of DTV is selected
2008-04-29 21:38:44 -03:00
#
2005-04-16 15:20:36 -07:00
media: Kconfig: better support hybrid TV devices
Right now, if one has an hybrid TV card, it has to select
both analog and digital TV support, as otherwise the needed
core support won't be selected.
Change the logic to auto-select the core support for those
drivers, as this is a way more intuitive.
It should be noticed that, as now both DVB_CORE and VIDEO_DEV
defaults depends on selecting a hybrid cards, we had to remove
the explicit dependencies there, in order to avoid circular
dependencies.
That requires some tricks:
1) the prompt should not be not visible when an hybrid card
is selected, as the user shold not change it.
2) When a media hybrid device is selected, the modular
option for DVB_CORE and VIDEO_DEV will follow the
MEDIA_SUPPORT dependency, as we can't have a core
built with "y" with a driver built as module.
Note: while here, moved two pure V4L2 PCI drivers out of the
"hybrid" part of config and consider pvrusb2 as an hybrid
device.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 08:36:36 +01:00
comment "Digital TV core enabled to support hybrid TV devices"
depends on MEDIA_HYBRID_USB || MEDIA_HYBRID_PCI
2008-04-29 21:38:44 -03:00
config DVB_CORE
2012-05-28 08:17:47 -03:00
tristate
media: Kconfig: better support hybrid TV devices
Right now, if one has an hybrid TV card, it has to select
both analog and digital TV support, as otherwise the needed
core support won't be selected.
Change the logic to auto-select the core support for those
drivers, as this is a way more intuitive.
It should be noticed that, as now both DVB_CORE and VIDEO_DEV
defaults depends on selecting a hybrid cards, we had to remove
the explicit dependencies there, in order to avoid circular
dependencies.
That requires some tricks:
1) the prompt should not be not visible when an hybrid card
is selected, as the user shold not change it.
2) When a media hybrid device is selected, the modular
option for DVB_CORE and VIDEO_DEV will follow the
MEDIA_SUPPORT dependency, as we can't have a core
built with "y" with a driver built as module.
Note: while here, moved two pure V4L2 PCI drivers out of the
"hybrid" part of config and consider pvrusb2 as an hybrid
device.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-25 08:36:36 +01:00
prompt "Digital TV core" if !(MEDIA_HYBRID_USB || MEDIA_HYBRID_PCI)
2012-05-28 08:17:47 -03:00
depends on MEDIA_DIGITAL_TV_SUPPORT
2018-03-07 09:51:17 -05:00
depends on (I2C || I2C=n)
2012-05-28 08:17:47 -03:00
default y
2008-04-29 21:38:44 -03:00
select CRC32
2007-08-27 21:59:35 -03:00
2017-12-28 09:24:20 -05:00
config DVB_MMAP
bool "Enable DVB memory-mapped API (EXPERIMENTAL)"
depends on DVB_CORE
2018-01-04 05:31:31 -05:00
depends on VIDEO_V4L2=y || VIDEO_V4L2=DVB_CORE
select VIDEOBUF2_VMALLOC
2017-12-28 09:24:20 -05:00
help
2018-01-16 22:16:12 -05:00
This option enables DVB experimental memory-mapped API, which
2017-12-28 09:24:20 -05:00
reduces the number of context switches to read DVB buffers, as
the buffers can use mmap() syscalls.
Support for it is experimental. Use with care. If unsure,
say N.
2011-05-23 09:43:35 -03:00
config DVB_NET
bool "DVB Network Support"
default (NET && INET)
2011-06-10 07:43:26 -03:00
depends on NET && INET && DVB_CORE
2011-05-23 09:43:35 -03:00
help
2011-06-16 16:06:56 -03:00
This option enables DVB Network Support which is a part of the DVB
standard. It is used, for example, by automatic firmware updates used
on Set-Top-Boxes. It can also be used to access the Internet via the
DVB card, if the network provider supports it.
2011-05-23 09:43:35 -03:00
2011-06-16 16:06:56 -03:00
You may want to disable the network support on embedded devices. If
unsure say Y.
2011-05-23 09:43:35 -03:00
2020-03-24 10:14:15 +01:00
source "drivers/media/v4l2-core/Kconfig"
source "drivers/media/mc/Kconfig"
2012-08-14 16:07:25 -03:00
source "drivers/media/dvb-core/Kconfig"
2020-03-24 10:14:15 +01:00
source "drivers/media/cec/Kconfig"
2012-08-14 16:07:25 -03:00
2012-07-06 09:12:59 -03:00
comment "Media drivers"
2007-08-23 16:37:49 -03:00
2012-06-14 16:35:56 -03:00
source "drivers/media/usb/Kconfig"
2012-08-20 10:02:05 -03:00
source "drivers/media/pci/Kconfig"
2020-03-24 10:27:15 +01:00
source "drivers/media/radio/Kconfig"
2020-03-24 10:14:15 +01:00
# Common driver options
source "drivers/media/common/Kconfig"
2020-03-24 10:27:15 +01:00
if MEDIA_PLATFORM_SUPPORT
2012-08-20 10:02:05 -03:00
source "drivers/media/platform/Kconfig"
media: split test drivers from platform directory
When the first test device was added (vivi.c), there were just
one file. I was too lazy on that time to create a separate
directory just for it, so I kept it together with platform.
Now, we have vivid, vicodec, vim2m and vimc. Also, a new
virtual driver has been prepared to support DVB API.
So, it is time to solve this mess, by placing test stuff
on a separate directory.
It should be noticed that we also have some skeleton drivers
(for V4L and for DVB). For now, we'll keep them separate,
as they're not really test drivers, but instead, just
examples. The DVB frontend ones will likely be part of a new DVB
test driver. By that time, it should make sense to move them
here as well.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
2020-03-24 10:39:43 +01:00
source "drivers/media/test_drivers/Kconfig"
2012-06-14 16:36:01 -03:00
source "drivers/media/mmc/Kconfig"
2020-03-24 10:27:15 +01:00
endif
2005-04-16 15:20:36 -07:00
2012-06-14 16:35:55 -03:00
source "drivers/media/firewire/Kconfig"
2016-09-15 12:18:14 -03:00
comment "Media ancillary drivers (tuners, sensors, i2c, spi, frontends)"
2012-12-22 07:48:58 -03:00
2012-08-20 10:02:05 -03:00
#
2016-09-15 12:18:14 -03:00
# Ancillary drivers (tuners, i2c, spi, frontends)
2012-08-20 10:02:05 -03:00
#
2012-08-20 14:48:02 -03:00
config MEDIA_SUBDRV_AUTOSELECT
2016-09-15 12:18:14 -03:00
bool "Autoselect ancillary drivers (tuners, sensors, i2c, spi, frontends)"
2014-07-12 21:43:12 -03:00
depends on MEDIA_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT || MEDIA_CAMERA_SUPPORT || MEDIA_SDR_SUPPORT
[media] subdev autoselect only works if I2C and I2C_MUX is selected
As reported by the kbuild test robot <fengguang.wu@intel.com>:
> warning: (VIDEO_EM28XX_DVB) selects DVB_M88DS3103 which has unmet direct dependencies (MEDIA_SUPPORT && DVB_CORE && I2C && I2C_MUX)
> drivers/built-in.o: In function `m88ds3103_release':
> >> m88ds3103.c:(.text+0x1ab1af): undefined reference to `i2c_del_mux_adapter'
> drivers/built-in.o: In function `m88ds3103_attach':
> >> (.text+0x1ab342): undefined reference to `i2c_add_mux_adapter'
There are 3 possible ways to fix it:
1) make em28xx dependent on I2C_MUX.
That sounds wrong, as the em28xx bridge doesn't have i2c muxes on it,
and just one frontend has.
Well, subdevs could eventually be converted to, instead of using dvb
i2c gate control, to use i2c mux support.
That makes sense, but it takes time and lots of effort. Not sure if
this will happen anytime soon.
2) MEDIA_SUBDRV_AUTOSELECT can be dependent of I2C and I2C_MUX.
That means that users will need to manually enable I2C_MUX on some
distributions. Not sure about others, but, on Fedora, this option is
disabled.
So, it can end by generating a number of complains from users
that their devices suddenly stopped working after a Kernel upgrade,
at least until all distros that ship Kernels with I2C_MUX enabled.
3) if MEDIA_SUBDRV_AUTOSELECT is selected, it will select I2C and I2C_MUX.
Of course, MEDIA_SUBDRV_AUTOSELECT will need to inherit all dependencies
that I2C and I2C_MUX have (only HAS_IOMEM).
The disadvantage is that, if new dependencies are added on I2C, they'll
also need to be added here.
As the hole idea of autoselect is to let the user not bother about whatever
frontend/tuner is used by a driver, IMHO, (3) is the better solution.
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-12-21 05:42:11 -02:00
depends on HAS_IOMEM
select I2C
select I2C_MUX
2019-07-15 17:23:15 -04:00
default y if !EMBEDDED
2012-08-20 14:48:02 -03:00
help
2012-12-22 07:48:58 -03:00
By default, a media driver auto-selects all possible ancillary
devices such as tuners, sensors, video encoders/decoders and
frontends, that are used by any of the supported devices.
2012-08-20 14:48:02 -03:00
This is generally the right thing to do, except when there
2012-10-17 16:09:23 -03:00
are strict constraints with regards to the kernel size,
like on embedded systems.
2012-08-20 14:48:02 -03:00
2012-10-17 16:09:23 -03:00
Use this option with care, as deselecting ancillary drivers which
are, in fact, necessary will result in the lack of the needed
functionality for your device (it may not tune or may not have
2012-12-22 07:48:58 -03:00
the needed demodulators).
2012-08-20 14:48:02 -03:00
If unsure say Y.
2019-07-27 10:31:29 -03:00
config MEDIA_HIDE_ANCILLARY_SUBDRV
2019-11-21 04:19:37 +01:00
bool
depends on MEDIA_SUBDRV_AUTOSELECT && !COMPILE_TEST && !EXPERT
default y
2019-07-27 10:31:29 -03:00
[media] Fix build when drivers are builtin and frontend modules
There are a large number of reports that the media build is
not compiling when some drivers are compiled as builtin, while
the needed frontends are compiled as module.
On the last one of such reports:
From: kbuild test robot <fengguang.wu@intel.com>
Subject: saa7134-dvb.c:undefined reference to `zl10039_attach'
The .config file has:
CONFIG_VIDEO_SAA7134=y
CONFIG_VIDEO_SAA7134_DVB=y
# CONFIG_MEDIA_ATTACH is not set
CONFIG_DVB_ZL10039=m
And it produces all those errors:
drivers/built-in.o: In function `set_type':
tuner-core.c:(.text+0x2f263e): undefined reference to `tea5767_attach'
tuner-core.c:(.text+0x2f273e): undefined reference to `tda9887_attach'
drivers/built-in.o: In function `tuner_probe':
tuner-core.c:(.text+0x2f2d20): undefined reference to `tea5767_autodetection'
drivers/built-in.o: In function `av7110_attach':
av7110.c:(.text+0x330bda): undefined reference to `ves1x93_attach'
av7110.c:(.text+0x330bf7): undefined reference to `stv0299_attach'
av7110.c:(.text+0x330c63): undefined reference to `tda8083_attach'
av7110.c:(.text+0x330d09): undefined reference to `ves1x93_attach'
av7110.c:(.text+0x330d33): undefined reference to `tda8083_attach'
av7110.c:(.text+0x330d5d): undefined reference to `stv0297_attach'
av7110.c:(.text+0x330dbe): undefined reference to `stv0299_attach'
drivers/built-in.o: In function `tuner_attach_dtt7520x':
ngene-cards.c:(.text+0x3381cb): undefined reference to `dvb_pll_attach'
drivers/built-in.o: In function `demod_attach_lg330x':
ngene-cards.c:(.text+0x33828a): undefined reference to `lgdt330x_attach'
drivers/built-in.o: In function `demod_attach_stv0900':
ngene-cards.c:(.text+0x3383d5): undefined reference to `stv090x_attach'
drivers/built-in.o: In function `cineS2_probe':
ngene-cards.c:(.text+0x338b7f): undefined reference to `drxk_attach'
drivers/built-in.o: In function `configure_tda827x_fe':
saa7134-dvb.c:(.text+0x346ae7): undefined reference to `tda10046_attach'
drivers/built-in.o: In function `dvb_init':
saa7134-dvb.c:(.text+0x347283): undefined reference to `mt352_attach'
saa7134-dvb.c:(.text+0x3472cd): undefined reference to `mt352_attach'
saa7134-dvb.c:(.text+0x34731c): undefined reference to `tda10046_attach'
saa7134-dvb.c:(.text+0x34733c): undefined reference to `tda10046_attach'
saa7134-dvb.c:(.text+0x34735c): undefined reference to `tda10046_attach'
saa7134-dvb.c:(.text+0x347378): undefined reference to `tda10046_attach'
saa7134-dvb.c:(.text+0x3473db): undefined reference to `tda10046_attach'
drivers/built-in.o:saa7134-dvb.c:(.text+0x347502): more undefined references to `tda10046_attach' follow
drivers/built-in.o: In function `dvb_init':
saa7134-dvb.c:(.text+0x347812): undefined reference to `mt352_attach'
saa7134-dvb.c:(.text+0x347951): undefined reference to `mt312_attach'
saa7134-dvb.c:(.text+0x3479a9): undefined reference to `mt312_attach'
>> saa7134-dvb.c:(.text+0x3479c1): undefined reference to `zl10039_attach'
This is happening because a builtin module can't use directly a symbol
found on a module. By enabling CONFIG_MEDIA_ATTACH, the configuration
becomes valid, as dvb_attach() macro loads the module if needed, making
the symbol available to the builtin module.
While this bug started to appear after the patches that use IS_DEFINED
macro (like changeset 7b34be71db533f3e0cf93d53cf62d036cdb5418a), this
bug is a way ancient than that.
The thing is that, before the IS_DEFINED() patches, the logic used to be:
&& defined(MODULE))
struct dvb_frontend *zl10039_attach(struct dvb_frontend *fe,
u8 i2c_addr,
struct i2c_adapter *i2c);
static inline struct dvb_frontend *zl10039_attach(struct dvb_frontend *fe,
u8 i2c_addr,
struct i2c_adapter *i2c)
{
printk(KERN_WARNING "%s: driver disabled by Kconfig\n", __func__);
return NULL;
}
The above code, with the .config file used, was evoluting to FALSE
(instead of TRUE as it should be, as CONFIG_DVB_ZL10039 is 'm'),
and were adding the static inline code at saa7134-dvb, instead
of the external call. So, while it weren't producing any compilation
error, the code weren't working either.
So, as the overhead for using CONFIG_MEDIA_ATTACH is minimal, just
enable it, if MODULES is defined.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2013-06-20 10:35:53 -03:00
config MEDIA_ATTACH
bool
depends on MEDIA_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT || MEDIA_RADIO_SUPPORT
depends on MODULES
default MODULES
2012-08-20 10:02:05 -03:00
source "drivers/media/i2c/Kconfig"
2016-09-15 12:18:14 -03:00
source "drivers/media/spi/Kconfig"
2012-08-20 14:48:02 -03:00
source "drivers/media/tuners/Kconfig"
2012-08-20 10:02:05 -03:00
source "drivers/media/dvb-frontends/Kconfig"
2009-05-18 22:00:34 -03:00
endif # MEDIA_SUPPORT
