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
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
|
|
|
|
|
|
menuconfig V4L_TEST_DRIVERS
|
|
|
|
|
bool "V4L test drivers"
|
2020-03-26 14:47:25 +00:00
|
|
|
depends on VIDEO_DEV
|
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
|
|
|
|
|
|
|
|
if V4L_TEST_DRIVERS
|
|
|
|
|
|
|
|
|
|
config VIDEO_VIM2M
|
|
|
|
|
tristate "Virtual Memory-to-Memory Driver"
|
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
|
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
|
|
|
select VIDEOBUF2_VMALLOC
|
|
|
|
|
select V4L2_MEM2MEM_DEV
|
2020-04-14 22:06:24 +00:00
|
|
|
select MEDIA_CONTROLLER
|
|
|
|
|
select MEDIA_CONTROLLER_REQUEST_API
|
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
|
|
|
|
|
This is a virtual test device for the memory-to-memory driver
|
|
|
|
|
framework.
|
|
|
|
|
|
2020-04-16 08:25:59 +00:00
|
|
|
source "drivers/media/test-drivers/vicodec/Kconfig"
|
2022-03-14 10:01:05 +00:00
|
|
|
source "drivers/media/test-drivers/vimc/Kconfig"
|
|
|
|
|
source "drivers/media/test-drivers/vivid/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 09:39:43 +00:00
|
|
|
|
|
|
|
|
endif #V4L_TEST_DRIVERS
|
2020-08-21 12:58:45 +00:00
|
|
|
|
2020-09-12 07:59:27 +00:00
|
|
|
menuconfig DVB_TEST_DRIVERS
|
|
|
|
|
bool "DVB test drivers"
|
|
|
|
|
depends on DVB_CORE && MEDIA_SUPPORT && I2C
|
|
|
|
|
help
|
|
|
|
|
Enables DVB test drivers.
|
|
|
|
|
|
|
|
|
|
This enables the DVB test drivers. They are meant as an aid for
|
|
|
|
|
DVB device driver writers and developers working on userspace
|
|
|
|
|
media applications.
|
|
|
|
|
|
2020-08-21 12:58:45 +00:00
|
|
|
if DVB_TEST_DRIVERS
|
|
|
|
|
|
|
|
|
|
source "drivers/media/test-drivers/vidtv/Kconfig"
|
|
|
|
|
|
|
|
|
|
endif #DVB_TEST_DRIVERS
|