From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: unlisted-recipients:; (no To-header on input)
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Michael Tretter" <m.tretter@pengutronix.de>,
"Ming Qian" <ming.qian@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: [PATCH v3 11/39] media: platform: allegro-dvt: move config to its own file
Date: Sun, 13 Mar 2022 08:21:20 +0100 [thread overview]
Message-ID: <589e645dd3740f269d80a3a17de13e74794e7f6b.1647155572.git.mchehab@kernel.org> (raw)
In-Reply-To: <cover.1647155572.git.mchehab@kernel.org>
In order to better organize the platform/Kconfig, place
allegro-dvt-specific config stuff on a separate Kconfig file.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v3 00/39] at: https://lore.kernel.org/all/cover.1647155572.git.mchehab@kernel.org/
drivers/media/platform/Kconfig | 17 +----------------
drivers/media/platform/allegro-dvt/Kconfig | 16 ++++++++++++++++
2 files changed, 17 insertions(+), 16 deletions(-)
create mode 100644 drivers/media/platform/allegro-dvt/Kconfig
diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
index b6650caecf45..25e5ae27210d 100644
--- a/drivers/media/platform/Kconfig
+++ b/drivers/media/platform/Kconfig
@@ -29,6 +29,7 @@ config V4L_MEM2MEM_DRIVERS
to capture and output drivers, which use memory buffers for just
one of those.
+source "drivers/media/platform/allegro-dvt/Kconfig"
source "drivers/media/platform/nxp/Kconfig"
source "drivers/media/platform/renesas/Kconfig"
@@ -176,22 +177,6 @@ config VIDEO_TI_CAL_MC
# Mem2mem drivers
-config VIDEO_ALLEGRO_DVT
- tristate "Allegro DVT Video IP Core"
- depends on V4L_MEM2MEM_DRIVERS
- depends on VIDEO_DEV && VIDEO_V4L2
- depends on ARCH_ZYNQMP || COMPILE_TEST
- select V4L2_MEM2MEM_DEV
- select VIDEOBUF2_DMA_CONTIG
- select REGMAP_MMIO
- help
- Support for the encoder video IP core by Allegro DVT. This core is
- found for example on the Xilinx ZynqMP SoC in the EV family and is
- called VCU in the reference manual.
-
- To compile this driver as a module, choose M here: the module
- will be called allegro.
-
config VIDEO_CODA
tristate "Chips&Media Coda multi-standard codec IP"
depends on V4L_MEM2MEM_DRIVERS
diff --git a/drivers/media/platform/allegro-dvt/Kconfig b/drivers/media/platform/allegro-dvt/Kconfig
new file mode 100644
index 000000000000..dd528e9d0958
--- /dev/null
+++ b/drivers/media/platform/allegro-dvt/Kconfig
@@ -0,0 +1,16 @@
+# SPDX-License-Identifier: GPL-2.0-only
+config VIDEO_ALLEGRO_DVT
+ tristate "Allegro DVT Video IP Core"
+ depends on V4L_MEM2MEM_DRIVERS
+ depends on VIDEO_DEV && VIDEO_V4L2
+ depends on ARCH_ZYNQMP || COMPILE_TEST
+ select V4L2_MEM2MEM_DEV
+ select VIDEOBUF2_DMA_CONTIG
+ select REGMAP_MMIO
+ help
+ Support for the encoder video IP core by Allegro DVT. This core is
+ found for example on the Xilinx ZynqMP SoC in the EV family and is
+ called VCU in the reference manual.
+
+ To compile this driver as a module, choose M here: the module
+ will be called allegro.
--
2.35.1
next prev parent reply other threads:[~2022-03-13 7:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 7:21 [PATCH v3 00/39] Sort Makefiles and platform/Kconfig Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 01/39] media: xc2028: rename the driver from tuner-xc2028 Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 02/39] media: Makefiles: remove extra spaces Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 03/39] media: Makefiles: sort entries where it fits Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 04/39] media: platform: Makefile: reorganize its contents Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 05/39] media: platform: move platform menu dependencies to drivers Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 06/39] media: platform: place Aspeed driver on a separate dir Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 07/39] media: platform: place NXP drivers " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 08/39] media: platform: place Intel " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 09/39] media: platform: place Via " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 10/39] media: platform: place Renesas " Mauro Carvalho Chehab
2022-03-13 7:21 ` Mauro Carvalho Chehab [this message]
2022-03-13 7:21 ` [PATCH v3 12/39] media: platform: amphion: move config to its own file Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 13/39] media: platform: coda: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 14/39] media: platform: exynos-gsc: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 15/39] media: platform: ge2d: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 16/39] media: platform: mtk-jpeg: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 17/39] media: platform: mtk-mdp: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 18/39] media: platform: mtk-vcodec: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 19/39] media: platform: mtk-vpu: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 20/39] media: platform: omap3isp: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 21/39] media: platform: camss: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 22/39] media: platform: venus: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 23/39] media: platform: rga: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 24/39] media: platform: s3c-camif: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 25/39] media: platform: s5p-g2d: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 26/39] media: platform: hva: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 27/39] media: platform: stm32: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 28/39] media: platform: sun8i-di: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 29/39] media: platform: sun8i-rotate: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 30/39] media: platform: vde: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 31/39] media: platform: ti-vpe: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 32/39] media: platform: rkisp1: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 33/39] media: platform: delta: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 34/39] media: platform: bdisp: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 35/39] media: platform: s5p-mfc: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 36/39] media: platform: s5p-jpeg: " Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 37/39] media: platform: Kconfig: sort entries Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 38/39] media: platform: move some manufacturer entries Mauro Carvalho Chehab
2022-03-13 7:21 ` [PATCH v3 39/39] media: platform: Kconfig: place platform drivers on a submenu Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=589e645dd3740f269d80a3a17de13e74794e7f6b.1647155572.git.mchehab@kernel.org \
--to=mchehab@kernel.org \
--cc=digetx@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jernej.skrabec@gmail.com \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=ming.qian@nxp.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®