2022-03-11 12:40:11 +01:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
|
|
|
|
|
|
# V4L drivers
|
2024-12-12 10:17:27 +01:00
|
|
|
config VIDEO_STM32_CSI
|
|
|
|
|
tristate "STM32 Camera Serial Interface (CSI) support"
|
|
|
|
|
depends on V4L_PLATFORM_DRIVERS
|
|
|
|
|
depends on VIDEO_DEV && OF
|
|
|
|
|
depends on ARCH_STM32 || COMPILE_TEST
|
|
|
|
|
select MEDIA_CONTROLLER
|
|
|
|
|
select V4L2_FWNODE
|
|
|
|
|
help
|
|
|
|
|
This module makes the STM32 Camera Serial Interface (CSI)
|
|
|
|
|
available as a v4l2 device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called stm32-csi.
|
|
|
|
|
|
2022-03-11 12:40:11 +01:00
|
|
|
config VIDEO_STM32_DCMI
|
|
|
|
|
tristate "STM32 Digital Camera Memory Interface (DCMI) support"
|
|
|
|
|
depends on V4L_PLATFORM_DRIVERS
|
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 07:25:46 +01:00
|
|
|
depends on VIDEO_DEV && OF
|
2022-03-11 12:40:11 +01:00
|
|
|
depends on ARCH_STM32 || COMPILE_TEST
|
|
|
|
|
select VIDEOBUF2_DMA_CONTIG
|
|
|
|
|
select MEDIA_CONTROLLER
|
|
|
|
|
select V4L2_FWNODE
|
|
|
|
|
help
|
|
|
|
|
This module makes the STM32 Digital Camera Memory Interface (DCMI)
|
|
|
|
|
available as a v4l2 device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called stm32-dcmi.
|
|
|
|
|
|
2023-11-27 18:08:17 +01:00
|
|
|
config VIDEO_STM32_DCMIPP
|
|
|
|
|
tristate "STM32 Digital Camera Memory Interface Pixel Processor (DCMIPP) support"
|
|
|
|
|
depends on V4L_PLATFORM_DRIVERS
|
|
|
|
|
depends on VIDEO_DEV
|
|
|
|
|
depends on ARCH_STM32 || COMPILE_TEST
|
|
|
|
|
select MEDIA_CONTROLLER
|
|
|
|
|
select VIDEOBUF2_DMA_CONTIG
|
|
|
|
|
select VIDEO_V4L2_SUBDEV_API
|
|
|
|
|
select V4L2_FWNODE
|
|
|
|
|
help
|
|
|
|
|
This module makes the STM32 Digital Camera Memory Interface
|
|
|
|
|
Pixel Processor (DCMIPP) available as a v4l2 device.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called stm32-dcmipp.
|
|
|
|
|
|
2022-03-11 12:40:11 +01:00
|
|
|
# Mem2mem drivers
|
|
|
|
|
config VIDEO_STM32_DMA2D
|
|
|
|
|
tristate "STM32 Chrom-Art Accelerator (DMA2D)"
|
|
|
|
|
depends on V4L_MEM2MEM_DRIVERS
|
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 07:25:46 +01:00
|
|
|
depends on VIDEO_DEV
|
2022-03-11 12:40:11 +01:00
|
|
|
depends on ARCH_STM32 || COMPILE_TEST
|
|
|
|
|
select VIDEOBUF2_DMA_CONTIG
|
|
|
|
|
select V4L2_MEM2MEM_DEV
|
|
|
|
|
help
|
|
|
|
|
Enables DMA2D hardware support on stm32.
|
|
|
|
|
|
|
|
|
|
The STM32 DMA2D is a memory-to-memory engine for pixel conversion
|
|
|
|
|
and specialized DMA dedicated to image manipulation.
|