2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# Multimedia device configuration
|
|
|
|
|
#
|
|
|
|
|
|
2020-04-15 07:46:06 +00:00
|
|
|
#
|
2020-04-15 07:55:10 +00:00
|
|
|
# NOTE: CEC and Remote Controller support should not depend on MEDIA_SUPPORT
|
2020-04-15 07:46:06 +00:00
|
|
|
#
|
2017-07-02 19:37:58 +00:00
|
|
|
source "drivers/media/rc/Kconfig"
|
2020-04-15 07:55:10 +00:00
|
|
|
source "drivers/media/cec/Kconfig"
|
2017-07-02 19:37:58 +00:00
|
|
|
|
2009-05-19 01:00:34 +00:00
|
|
|
menuconfig MEDIA_SUPPORT
|
|
|
|
|
tristate "Multimedia support"
|
2007-05-10 13:45:57 +00:00
|
|
|
depends on HAS_IOMEM
|
2009-05-19 01:00:34 +00:00
|
|
|
help
|
2020-03-24 09:15:43 +00: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 11:17:47 +00:00
|
|
|
Additional info and docs are available on the web at
|
2015-12-04 12:38:59 +00:00
|
|
|
<https://linuxtv.org>
|
2009-05-19 01:00:34 +00:00
|
|
|
|
2020-03-24 10:36:10 +00:00
|
|
|
if MEDIA_SUPPORT
|
|
|
|
|
|
|
|
|
|
config MEDIA_SUPPORT_FILTER
|
2020-03-26 08:44:13 +00:00
|
|
|
bool "Filter media drivers"
|
2022-09-08 10:43:34 +00:00
|
|
|
default y if !EXPERT
|
2020-03-24 10:36:10 +00:00
|
|
|
help
|
|
|
|
|
Configuring the media subsystem can be complex, as there are
|
|
|
|
|
hundreds of drivers and other config options.
|
|
|
|
|
|
|
|
|
|
This menu offers option that will help the Kernel's config
|
|
|
|
|
system to hide drivers that are out of the scope of the
|
|
|
|
|
user needs, and disabling core support for unused APIs.
|
|
|
|
|
|
|
|
|
|
If not selected, all non-optional media core functionality
|
|
|
|
|
needed to support media drivers will be enabled. Also, all
|
|
|
|
|
media device drivers should be shown.
|
|
|
|
|
|
2020-03-24 13:24:41 +00:00
|
|
|
config MEDIA_SUBDRV_AUTOSELECT
|
|
|
|
|
bool "Autoselect ancillary drivers (tuners, sensors, i2c, spi, frontends)"
|
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
|
select I2C
|
|
|
|
|
select I2C_MUX
|
|
|
|
|
default y if MEDIA_SUPPORT_FILTER
|
|
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
This is generally the right thing to do, except when there
|
|
|
|
|
are strict constraints with regards to the kernel size,
|
|
|
|
|
like on embedded systems.
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
the needed demodulators).
|
|
|
|
|
|
|
|
|
|
If unsure say Y.
|
|
|
|
|
|
2020-03-24 10:36:10 +00:00
|
|
|
menu "Media device types"
|
2008-04-30 00:38:44 +00:00
|
|
|
|
2012-05-28 11:17:47 +00:00
|
|
|
#
|
|
|
|
|
# Multimedia support - automatically enable V4L2 and DVB core
|
|
|
|
|
#
|
|
|
|
|
config MEDIA_CAMERA_SUPPORT
|
2020-03-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "Cameras and video grabbers" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
2019-03-20 10:39:44 +00:00
|
|
|
help
|
2012-05-28 11:17:47 +00: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-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "Analog TV" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
2019-03-20 10:39:44 +00:00
|
|
|
help
|
2012-05-28 11:17:47 +00:00
|
|
|
Enable analog TV support.
|
|
|
|
|
|
2020-04-14 09:00:30 +00:00
|
|
|
Say Y when you have a TV board with analog support or with a
|
|
|
|
|
hybrid analog/digital TV chipset.
|
|
|
|
|
|
|
|
|
|
Note: There are several DVB cards that are based on chips that
|
|
|
|
|
support both analog and digital TV. Disabling this option
|
|
|
|
|
will disable support for them.
|
2012-05-28 11:17:47 +00:00
|
|
|
|
|
|
|
|
config MEDIA_DIGITAL_TV_SUPPORT
|
2020-03-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "Digital TV" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
2019-03-20 10:39:44 +00:00
|
|
|
help
|
2012-05-28 11:17:47 +00:00
|
|
|
Enable digital TV support.
|
|
|
|
|
|
2020-04-14 09:00:30 +00:00
|
|
|
Say Y when you have a board with digital support or a board with
|
|
|
|
|
hybrid digital TV and analog TV.
|
2012-05-28 11:17:47 +00:00
|
|
|
|
|
|
|
|
config MEDIA_RADIO_SUPPORT
|
2020-03-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "AM/FM radio receivers/transmitters" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
2019-03-20 10:39:44 +00:00
|
|
|
help
|
2012-05-28 11:17:47 +00:00
|
|
|
Enable AM/FM radio support.
|
|
|
|
|
|
|
|
|
|
Additional info and docs are available on the web at
|
2015-12-04 12:38:59 +00:00
|
|
|
<https://linuxtv.org>
|
2012-05-28 11:17:47 +00:00
|
|
|
|
|
|
|
|
Say Y when you have a board with radio support.
|
|
|
|
|
|
2020-04-14 09:00:30 +00:00
|
|
|
Note: There are several TV cards that are based on chips that
|
|
|
|
|
support radio reception. Disabling this option will
|
|
|
|
|
disable support for them.
|
|
|
|
|
|
2014-07-13 00:43:12 +00:00
|
|
|
config MEDIA_SDR_SUPPORT
|
2020-03-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "Software defined radio" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
2019-03-20 10:39:44 +00:00
|
|
|
help
|
2014-07-13 00:43:12 +00:00
|
|
|
Enable software defined radio support.
|
|
|
|
|
|
|
|
|
|
Say Y when you have a software defined radio device.
|
|
|
|
|
|
2020-03-24 09:27:15 +00:00
|
|
|
config MEDIA_PLATFORM_SUPPORT
|
2020-03-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "Platform-specific devices" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
2020-03-24 09:27:15 +00: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.
|
|
|
|
|
|
2021-03-10 14:58:16 +00:00
|
|
|
Say Y when you want to be able to see such devices.
|
2020-03-24 09:27:15 +00:00
|
|
|
|
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 09:39:43 +00:00
|
|
|
config MEDIA_TEST_SUPPORT
|
2020-03-25 15:33:35 +00:00
|
|
|
bool
|
|
|
|
|
prompt "Test drivers" if MEDIA_SUPPORT_FILTER
|
2020-03-24 10:36:10 +00:00
|
|
|
default y if !MEDIA_SUPPORT_FILTER
|
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 09:39:43 +00:00
|
|
|
help
|
2021-11-07 18:19:23 +00:00
|
|
|
These drivers should not be used on production kernels, but
|
|
|
|
|
can be useful on debug ones. This option enables several dummy drivers
|
|
|
|
|
that simulate real hardware. Very useful to test userspace
|
|
|
|
|
applications and to validate if the subsystem core doesn't
|
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 09:39:43 +00:00
|
|
|
have regressions.
|
|
|
|
|
|
|
|
|
|
Say Y if you want to use some virtual test driver.
|
|
|
|
|
|
|
|
|
|
In case of doubts, say N.
|
2020-03-24 09:25:09 +00:00
|
|
|
Say Y when you have a software defined radio device.
|
2020-03-24 10:36:10 +00:00
|
|
|
endmenu # media device types
|
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 09:39:43 +00:00
|
|
|
|
2018-12-05 17:23:54 +00:00
|
|
|
|
2020-03-24 13:09:23 +00:00
|
|
|
menu "Media core support"
|
|
|
|
|
visible if !MEDIA_SUPPORT_FILTER
|
2008-04-30 00:38:44 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config VIDEO_DEV
|
2020-04-14 09:00:30 +00:00
|
|
|
tristate "Video4Linux core"
|
|
|
|
|
default MEDIA_CAMERA_SUPPORT || MEDIA_ANALOG_TV_SUPPORT || MEDIA_RADIO_SUPPORT || MEDIA_SDR_SUPPORT || MEDIA_PLATFORM_SUPPORT || MEDIA_TEST_SUPPORT
|
media: Kconfig: cleanup VIDEO_DEV dependencies
media Kconfig has two entries associated to V4L API:
VIDEO_DEV and VIDEO_V4L2.
On Kernel 2.6.x, there were two V4L APIs, each one with its own flag.
VIDEO_DEV were meant to:
1) enable Video4Linux and make its Kconfig options to appear;
2) it makes the Kernel build the V4L core.
while VIDEO_V4L2 where used to distinguish between drivers that
implement the newer API and drivers that implemented the former one.
With time, such meaning changed, specially after the removal of
all V4L version 1 drivers.
At the current implementation, VIDEO_DEV only does (1): it enables
the media options related to V4L, that now has:
menu "Video4Linux options"
visible if VIDEO_DEV
source "drivers/media/v4l2-core/Kconfig"
endmenu
but it doesn't affect anymore the V4L core drivers.
The rationale is that the V4L2 core has a "soft" dependency
at the I2C bus, and now requires to select a number of other
Kconfig options:
config VIDEO_V4L2
tristate
depends on (I2C || I2C=n) && VIDEO_DEV
select RATIONAL
select VIDEOBUF2_V4L2 if VIDEOBUF2_CORE
default (I2C || I2C=n) && VIDEO_DEV
In the past, merging them would be tricky, but it seems that it is now
possible to merge those symbols, in order to simplify V4L dependencies.
Let's keep VIDEO_DEV, as this one is used on some make *defconfig
configurations.
Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com> # for meson-vdec & meson-ge2d
Acked-by: Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>
Acked-by: Łukasz Stelmach <l.stelmach@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
2022-03-13 06:25:46 +00:00
|
|
|
depends on (I2C || I2C=n)
|
|
|
|
|
select RATIONAL
|
|
|
|
|
select VIDEOBUF2_V4L2 if VIDEOBUF2_CORE
|
2020-03-24 13:09:23 +00:00
|
|
|
help
|
|
|
|
|
Enables the V4L2 API, used by cameras, analog TV, video grabbers,
|
|
|
|
|
radio devices and by some input devices.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-03-24 12:59:23 +00:00
|
|
|
config MEDIA_CONTROLLER
|
|
|
|
|
bool "Media Controller API"
|
|
|
|
|
default MEDIA_CAMERA_SUPPORT || MEDIA_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT || MEDIA_PLATFORM_SUPPORT
|
|
|
|
|
help
|
|
|
|
|
Enable the media controller API used to query media devices internal
|
|
|
|
|
topology and configure it dynamically.
|
|
|
|
|
|
|
|
|
|
This API is mostly used by camera interfaces in embedded platforms.
|
|
|
|
|
|
2008-04-30 00:38:44 +00:00
|
|
|
#
|
|
|
|
|
# DVB Core
|
2012-05-28 11:17:47 +00:00
|
|
|
# Only enables if one of DTV is selected
|
2008-04-30 00:38:44 +00:00
|
|
|
#
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-04-30 00:38:44 +00:00
|
|
|
config DVB_CORE
|
2022-05-16 17:15:15 +00:00
|
|
|
tristate "DVB Core"
|
2012-05-28 11:17:47 +00:00
|
|
|
depends on MEDIA_DIGITAL_TV_SUPPORT
|
2018-03-07 14:51:17 +00:00
|
|
|
depends on (I2C || I2C=n)
|
2020-04-15 08:06:59 +00:00
|
|
|
default MEDIA_DIGITAL_TV_SUPPORT
|
2008-04-30 00:38:44 +00:00
|
|
|
select CRC32
|
2017-12-28 14:24:20 +00:00
|
|
|
help
|
2020-03-24 13:09:23 +00:00
|
|
|
Enables the DVB API, used by Digital TV devices. Supports several
|
|
|
|
|
standards, including DVB, ATSC, ISDB and CMDB.
|
2017-12-28 14:24:20 +00:00
|
|
|
|
2020-03-24 13:09:23 +00:00
|
|
|
endmenu # Media core support
|
2017-12-28 14:24:20 +00:00
|
|
|
|
2020-03-24 13:09:23 +00:00
|
|
|
#
|
|
|
|
|
# Extra per-media API core functionality
|
2011-05-23 12:43:35 +00:00
|
|
|
|
2020-03-25 10:15:15 +00:00
|
|
|
menu "Video4Linux options"
|
|
|
|
|
visible if VIDEO_DEV
|
|
|
|
|
|
2020-03-24 09:14:15 +00:00
|
|
|
source "drivers/media/v4l2-core/Kconfig"
|
2020-03-25 10:15:15 +00:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
menu "Media controller options"
|
|
|
|
|
visible if MEDIA_CONTROLLER
|
|
|
|
|
|
2020-03-24 09:14:15 +00:00
|
|
|
source "drivers/media/mc/Kconfig"
|
2020-03-25 10:15:15 +00:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
menu "Digital TV options"
|
|
|
|
|
visible if DVB_CORE
|
|
|
|
|
|
2012-08-14 19:07:25 +00:00
|
|
|
source "drivers/media/dvb-core/Kconfig"
|
2020-03-25 10:15:15 +00:00
|
|
|
endmenu
|
|
|
|
|
|
2020-03-24 13:09:23 +00:00
|
|
|
menu "Media drivers"
|
2007-08-23 19:37:49 +00:00
|
|
|
|
2020-03-26 08:44:13 +00:00
|
|
|
comment "Drivers filtered as selected at 'Filter media drivers'"
|
|
|
|
|
depends on MEDIA_SUPPORT_FILTER
|
|
|
|
|
|
2022-03-13 05:47:32 +00:00
|
|
|
comment "Media drivers"
|
|
|
|
|
|
2012-06-14 19:35:56 +00:00
|
|
|
source "drivers/media/usb/Kconfig"
|
2012-08-20 13:02:05 +00:00
|
|
|
source "drivers/media/pci/Kconfig"
|
2020-03-24 09:27:15 +00:00
|
|
|
source "drivers/media/radio/Kconfig"
|
|
|
|
|
|
|
|
|
|
if MEDIA_PLATFORM_SUPPORT
|
2012-08-20 13:02:05 +00:00
|
|
|
source "drivers/media/platform/Kconfig"
|
2012-06-14 19:36:01 +00:00
|
|
|
source "drivers/media/mmc/Kconfig"
|
2020-03-24 09:27:15 +00:00
|
|
|
endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-04-15 13:35:52 +00:00
|
|
|
if MEDIA_TEST_SUPPORT
|
2020-04-16 08:25:59 +00:00
|
|
|
source "drivers/media/test-drivers/Kconfig"
|
2020-04-15 13:35:52 +00:00
|
|
|
endif
|
|
|
|
|
|
2012-06-14 19:35:55 +00:00
|
|
|
source "drivers/media/firewire/Kconfig"
|
|
|
|
|
|
2022-03-13 05:47:32 +00:00
|
|
|
# Common driver options
|
|
|
|
|
source "drivers/media/common/Kconfig"
|
|
|
|
|
|
2020-03-24 13:09:23 +00:00
|
|
|
endmenu
|
|
|
|
|
|
2012-08-20 13:02:05 +00:00
|
|
|
#
|
2016-09-15 15:18:14 +00:00
|
|
|
# Ancillary drivers (tuners, i2c, spi, frontends)
|
2012-08-20 13:02:05 +00:00
|
|
|
#
|
|
|
|
|
|
2019-07-27 13:31:29 +00:00
|
|
|
config MEDIA_HIDE_ANCILLARY_SUBDRV
|
2019-11-21 03:19:37 +00:00
|
|
|
bool
|
|
|
|
|
depends on MEDIA_SUBDRV_AUTOSELECT && !COMPILE_TEST && !EXPERT
|
|
|
|
|
default y
|
2019-07-27 13:31:29 +00:00
|
|
|
|
2020-03-24 13:24:41 +00:00
|
|
|
menu "Media ancillary drivers"
|
|
|
|
|
|
[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 13:35:53 +00: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 13:02:05 +00:00
|
|
|
source "drivers/media/i2c/Kconfig"
|
2016-09-15 15:18:14 +00:00
|
|
|
source "drivers/media/spi/Kconfig"
|
2012-08-20 17:48:02 +00:00
|
|
|
source "drivers/media/tuners/Kconfig"
|
2012-08-20 13:02:05 +00:00
|
|
|
source "drivers/media/dvb-frontends/Kconfig"
|
|
|
|
|
|
2020-03-24 13:09:23 +00:00
|
|
|
endmenu
|
|
|
|
|
|
2009-05-19 01:00:34 +00:00
|
|
|
endif # MEDIA_SUPPORT
|
