kernel/drivers/media/dvb-frontends/Kconfig, branch linux-6.9.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.9.y2022-03-18T04:58:35Zmedia: media/*/Kconfig: sort entries2022-03-18T04:58:35ZMauro Carvalho Chehabmchehab@kernel.org2022-03-14T10:01:05Zurn:sha1:6cdc31b2d7095af3d39f001b0d4e367a6f32664e
Currently, the idems inside media Kconfig are out of order.
Sort them using the script below:
<script>
use strict;
use warnings;
my %config;
my @source;
my $out;
sub flush_config()
{
if (scalar %config) {
for my $c (sort keys %config) {
$out .= $config{$c} . "\n";
}
%config = ();
}
return if (!scalar @source);
$out .= "\n";
for my $s (sort @source) {
$out .= $s;
}
$out .= "\n";
@source = ();
}
sub sort_kconfig($)
{
my $fname = shift;
my $cur_config = "";
@source = ();
$out = "";
%config = ();
open IN, $fname or die;
while (<IN>) {
if (m/^config\s+(.*)/) {
$cur_config = $1;
$config{$cur_config} .= $_;
} elsif (m/^source\s+(.*)/) {
push @source, $_;
} elsif (m/^\s+/) {
if ($cur_config eq "") {
$out .= $_;
} else {
$config{$cur_config} .= $_;
}
} else {
flush_config();
$cur_config = "";
$out .= $_;
}
}
close IN or die;
flush_config();
$out =~ s/\n\n+/\n\n/g;
$out =~ s/\n+$/\n/;
open OUT, ">$fname";
print OUT $out;
close OUT;
}
for my $fname(@ARGV) {
sort_kconfig $fname
}
</script>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
media: Kconfig: cleanup VIDEO_DEV dependencies2022-03-18T04:58:35ZMauro Carvalho Chehabmchehab@kernel.org2022-03-13T06:25:46Zurn:sha1:9958d30f38b96fb763a10d44d18ddad39127d5f4
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>
media: sp8870: move it to staging2021-06-02T09:17:03ZMauro Carvalho Chehabmchehab+huawei@kernel.org2021-05-31T20:34:24Zurn:sha1:b998a59f82f1152605eae4f7617778020549e81a
This driver is used only by av7110, which is preparing for
its retirement. So, move this ancillary driver to stay together
with av7110.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: mxl692: MaxLinear 692 ATSC demod/tuner driver2021-02-05T22:37:59ZBrad Lovebrad@nextdimension.cc2021-01-26T01:54:13Zurn:sha1:b53f2fa136b1b20f03184f4a98fea75eb2705eac
MaxLinear 692 is a combo demod/tuner which has ATSC and QAM
capabilities. Only ATSC is currently advertised via DVB
properties. QAM still has issues.
Confirmed working on both big and little endian. Big
endian verified on PowerPC Mac mini.
Signed-off-by: Brad Love <brad@nextdimension.cc>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: Fix RTL2832 not depending on REGMAP_I2C2021-01-27T13:42:23ZMaxim Plotnikovwgh@torlan.ru2020-12-01T00:14:27Zurn:sha1:65fba0b15e99606f094d688bc562168834d214dd
Prevents this compile time error:
ERROR: modpost: "__regmap_init_i2c" [drivers/media/dvb-frontends/rtl2832.ko] undefined!
Signed-off-by: Maxim Plotnikov <wgh@torlan.ru>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: dvb-frontends: DUMMY_FE should depends on DVB_CORE2020-04-17T07:21:47ZMauro Carvalho Chehabmchehab+huawei@kernel.org2020-04-17T07:13:38Zurn:sha1:ceab3ac1e60d70afb4e25147d60817c513f235f7
Using select for DVB_CORE doesn't work, as reported by
Randy:
CONFIG_I2C=m
CONFIG_DVB_CORE=y
ld: drivers/media/dvb-core/dvbdev.o: in function `dvb_module_probe':
dvbdev.c:(.text+0xf92): undefined reference to `i2c_new_client_device'
ld: dvbdev.c:(.text+0xffb): undefined reference to `i2c_unregister_device'
ld: drivers/media/dvb-core/dvbdev.o: in function `dvb_module_release':
dvbdev.c:(.text+0x107d): undefined reference to `i2c_unregister_device'
The problem is actually caused by the dummy frontend driver,
which uses select, and it is missing an I2C dependency:
WARNING: unmet direct dependencies detected for DVB_CORE
Depends on [m]: MEDIA_SUPPORT [=y] && MEDIA_DIGITAL_TV_SUPPORT [=y] && (I2C [=m] || I2C [=m]=n)
Selected by [y]:
- DVB_DUMMY_FE [=y] && MEDIA_SUPPORT [=y] && MEDIA_TEST_SUPPORT [=y]
As this is the only frontend driver using "select DVB_CORE",
change it do depends on DVB_CORE.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: i2c/Kconfig: use sub-menus for I2C support2020-04-16T08:34:40ZMauro Carvalho Chehabmchehab+huawei@kernel.org2020-04-15T13:39:38Zurn:sha1:5c57ae64e8bccc693a96b4bbd9b20cc5890aeb69
There are *lots* of I2C ancillary drivers. While we're using
comments to group them, all options appear at the same menu.
It should be a lot clearer to group them into sub-menus, with
may help people to go directly to the driver(s) he's needing
to enable.
Suggested-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Acked-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: add SPDX headers on Kconfig and Makefile files2020-04-14T08:29:05ZMauro Carvalho Chehabmchehab+huawei@kernel.org2020-03-26T15:13:16Zurn:sha1:76c34a8d0e53f98975a2da5f753a99b4abc05c44
Most of media Kconfig/Makefile files already has SPDX,
but there are a few ones still missing. Add it to them.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: Kconfig: fix selection for test drivers2020-04-14T08:29:05ZMauro Carvalho Chehabmchehab+huawei@kernel.org2020-03-26T14:47:25Zurn:sha1:6268b351394450e9168a9281a9279f7cb420669f
There are some long-time mistakes related to build test
drivers, with regards to depends on/select. Also, as we
now want to build any test driver without needing to
enable anything else, change the logic in order to properly
filter them.
Please notice that the PCI skeleton is somewhat an
exception, as it requires to select *both* SAMPLES and
MEDIA_TEST_SUPPORT. I almost changed it to be either one,
but decided to keep it as-is, as this is something that
we don't really need to be included on any distribution.
The only reason for someone to build it is for COMPILE_TEST
purposes.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
media: Kconfig: mark other drivers as test drivers2020-04-14T08:29:05ZMauro Carvalho Chehabmchehab+huawei@kernel.org2020-03-26T08:45:31Zurn:sha1:97b19498dc0250826f6c9f4921b1e4c553cb086c
Neither the PCI skeleton nor the DVB dummy driver are real
drivers. They're there just as an example for a driver
writter.
Distros should not enable those drivers. So, hide them if
MEDIA_TEST_SUPPORT is not selected.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>