2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2012-06-14 19:35:53 +00:00
|
|
|
#
|
|
|
|
|
# DVB device configuration
|
|
|
|
|
#
|
|
|
|
|
|
2020-03-24 12:47:11 +00:00
|
|
|
config DVB_MMAP
|
|
|
|
|
bool "Enable DVB memory-mapped API (EXPERIMENTAL)"
|
|
|
|
|
depends on DVB_CORE
|
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 VIDEO_DEV=y || VIDEO_DEV=DVB_CORE
|
2020-03-24 12:47:11 +00:00
|
|
|
select VIDEOBUF2_VMALLOC
|
|
|
|
|
help
|
|
|
|
|
This option enables DVB experimental memory-mapped API, which
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config DVB_NET
|
|
|
|
|
bool "DVB Network Support"
|
|
|
|
|
default (NET && INET)
|
|
|
|
|
depends on NET && INET && DVB_CORE
|
|
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
You may want to disable the network support on embedded devices. If
|
|
|
|
|
unsure say Y.
|
|
|
|
|
|
2012-06-14 19:35:53 +00:00
|
|
|
config DVB_MAX_ADAPTERS
|
|
|
|
|
int "maximum number of DVB/ATSC adapters"
|
|
|
|
|
depends on DVB_CORE
|
2016-04-05 16:14:10 +00:00
|
|
|
default 16
|
2012-06-14 19:35:53 +00:00
|
|
|
range 1 255
|
|
|
|
|
help
|
|
|
|
|
Maximum number of DVB/ATSC adapters. Increasing this number
|
|
|
|
|
increases the memory consumption of the DVB subsystem even
|
|
|
|
|
if a much lower number of DVB/ATSC adapters is present.
|
|
|
|
|
Only values in the range 4-32 are tested.
|
|
|
|
|
|
2016-04-05 16:14:10 +00:00
|
|
|
If you are unsure about this, use the default value 16
|
2012-06-14 19:35:53 +00:00
|
|
|
|
|
|
|
|
config DVB_DYNAMIC_MINORS
|
|
|
|
|
bool "Dynamic DVB minor allocation"
|
|
|
|
|
depends on DVB_CORE
|
2020-03-25 14:01:25 +00:00
|
|
|
default y
|
2012-06-14 19:35:53 +00:00
|
|
|
help
|
|
|
|
|
If you say Y here, the DVB subsystem will use dynamic minor
|
|
|
|
|
allocation for any device that uses the DVB major number.
|
|
|
|
|
This means that you can have more than 4 of a single type
|
|
|
|
|
of device (like demuxes and frontends) per adapter, but udev
|
|
|
|
|
will be required to manage the device nodes.
|
|
|
|
|
|
|
|
|
|
If you are unsure about this, say N here.
|
2016-10-13 09:57:47 +00:00
|
|
|
|
|
|
|
|
config DVB_DEMUX_SECTION_LOSS_LOG
|
|
|
|
|
bool "Enable DVB demux section packet loss log"
|
|
|
|
|
depends on DVB_CORE
|
|
|
|
|
help
|
|
|
|
|
Enable extra log messages meant to detect packet loss
|
|
|
|
|
inside the Kernel.
|
|
|
|
|
|
|
|
|
|
Should not be enabled on normal cases, as logs can
|
|
|
|
|
be very verbose.
|
|
|
|
|
|
|
|
|
|
If you are unsure about this, say N here.
|
2017-12-11 16:37:26 +00:00
|
|
|
|
|
|
|
|
config DVB_ULE_DEBUG
|
|
|
|
|
bool "Enable DVB net ULE packet debug messages"
|
|
|
|
|
depends on DVB_CORE
|
|
|
|
|
help
|
|
|
|
|
Enable extra log messages meant to detect problems while
|
|
|
|
|
handling DVB network ULE packet loss inside the Kernel.
|
|
|
|
|
|
|
|
|
|
Should not be enabled on normal cases, as logs can
|
|
|
|
|
be very verbose.
|
|
|
|
|
|
|
|
|
|
If you are unsure about this, say N here.
|