From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: bingbu.cao@intel.com, linux-media@vger.kernel.org,
sakari.ailus@linux.intel.com, hdegoede@redhat.com
Cc: hans@hansg.org, stanislaw.gruszka@linux.intel.com
Subject: Re: [RFC PATCH 7/7] media: ipu7: add Makefile and Kconfig for IPU7
Date: Tue, 25 Feb 2025 13:55:40 +0800 [thread overview]
Message-ID: <1f46cbd1-384a-44f8-4ec1-414409ded771@linux.intel.com> (raw)
In-Reply-To: <20250221075252.3347582-8-bingbu.cao@intel.com>
All,
On 2/21/25 3:52 PM, bingbu.cao@intel.com wrote:
> From: Bingbu Cao <bingbu.cao@intel.com>
>
> Add Kconfig and Makefile for IPU7 driver and also update
> the Makefile to build the IPU7 driver.
>
> Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
> ---
> drivers/media/pci/intel/Kconfig | 1 +
> drivers/media/pci/intel/Makefile | 1 +
> drivers/media/pci/intel/ipu7/Kconfig | 18 ++++++++++++++++++
> drivers/media/pci/intel/ipu7/Makefile | 23 +++++++++++++++++++++++
> 4 files changed, 43 insertions(+)
> create mode 100644 drivers/media/pci/intel/ipu7/Kconfig
> create mode 100644 drivers/media/pci/intel/ipu7/Makefile
>
> diff --git a/drivers/media/pci/intel/Kconfig b/drivers/media/pci/intel/Kconfig
> index d9fcddce028b..948cda08fff5 100644
> --- a/drivers/media/pci/intel/Kconfig
> +++ b/drivers/media/pci/intel/Kconfig
> @@ -2,6 +2,7 @@
>
> source "drivers/media/pci/intel/ipu3/Kconfig"
> source "drivers/media/pci/intel/ipu6/Kconfig"
> +source "drivers/media/pci/intel/ipu7/Kconfig"
> source "drivers/media/pci/intel/ivsc/Kconfig"
>
> config IPU_BRIDGE
> diff --git a/drivers/media/pci/intel/Makefile b/drivers/media/pci/intel/Makefile
> index 3a2cc6567159..ff0fea13422d 100644
> --- a/drivers/media/pci/intel/Makefile
> +++ b/drivers/media/pci/intel/Makefile
> @@ -6,3 +6,4 @@ obj-$(CONFIG_IPU_BRIDGE) += ipu-bridge.o
> obj-y += ipu3/
> obj-y += ivsc/
> obj-$(CONFIG_VIDEO_INTEL_IPU6) += ipu6/
> +obj-$(CONFIG_VIDEO_INTEL_IPU7) += ipu7/
> diff --git a/drivers/media/pci/intel/ipu7/Kconfig b/drivers/media/pci/intel/ipu7/Kconfig
> new file mode 100644
> index 000000000000..b759d5e6c3a9
> --- /dev/null
> +++ b/drivers/media/pci/intel/ipu7/Kconfig
> @@ -0,0 +1,18 @@
> +config VIDEO_INTEL_IPU7
> + tristate "Intel IPU7 driver"
> + depends on ACPI || COMPILE_TEST
> + depends on VIDEO_DEV
> + depends on X86 && X86_64 && HAS_DMA
depends on X86 && HAS_DMA
> + depends on IPU_BRIDGE || !IPU_BRIDGE
> + select AUXILIARY_BUS
> + select IOMMU_IOVA
> + select VIDEO_V4L2_SUBDEV_API
> + select MEDIA_CONTROLLER
> + select VIDEOBUF2_DMA_CONTIG
This should be VIDEOBUF2_DMA_SG, I forgot to amend it.
> + select V4L2_FWNODE
> + help
> + This is the 7th Gen Intel Image Processing Unit, found in Intel SoCs
> + and used for capturing images and video from camera sensors.
> +
> + To compile this driver, say Y here! It contains 2 modules -
> + intel_ipu7 and intel_ipu7_isys.
> diff --git a/drivers/media/pci/intel/ipu7/Makefile b/drivers/media/pci/intel/ipu7/Makefile
> new file mode 100644
> index 000000000000..9a15d119026a
> --- /dev/null
> +++ b/drivers/media/pci/intel/ipu7/Makefile
> @@ -0,0 +1,23 @@
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2017 - 2024 Intel Corporation.
> +
> +intel-ipu7-objs += ipu7.o \
> + ipu7-bus.o \
> + ipu7-dma.o \
> + ipu7-mmu.o \
> + ipu7-buttress.o \
> + ipu7-cpd.o \
> + ipu7-syscom.o \
> + ipu7-boot.o
> +
> +obj-$(CONFIG_VIDEO_INTEL_IPU7) += intel-ipu7.o
> +
> +intel-ipu7-isys-objs += ipu7-isys.o \
> + ipu7-isys-csi2.o \
> + ipu7-isys-csi-phy.o \
> + ipu7-fw-isys.o \
> + ipu7-isys-video.o \
> + ipu7-isys-queue.o \
> + ipu7-isys-subdev.o
> +
> +obj-$(CONFIG_VIDEO_INTEL_IPU7) += intel-ipu7-isys.o
>
--
Best regards,
Bingbu Cao
next prev parent reply other threads:[~2025-02-25 6:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 7:52 [RFC PATCH 0/7] Intel IPU7 PCI and input system device drivers bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 1/7] media: Rename the IPU PCI device table header and add IPU7 PCI IDs bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 2/7] media: ipu7: add Intel IPU7 PCI device driver bingbu.cao
2025-02-24 14:38 ` Philipp Stanner
2025-02-25 9:39 ` Bingbu Cao
2025-02-27 4:06 ` Bingbu Cao
2025-03-03 15:01 ` Philipp Stanner
2025-03-03 15:18 ` Philipp Stanner
2025-02-26 10:00 ` Philipp Stanner
2025-02-27 3:47 ` Bingbu Cao
2025-02-21 7:52 ` [RFC PATCH 3/7] media: ipu7: add IPU7 DMA APIs and MMU mapping bingbu.cao
2025-03-03 16:13 ` Bjorn Helgaas
2025-02-21 7:52 ` [RFC PATCH 4/7] media: ipu7: add firmware parse, syscom interface and boot sequence bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 5/7] media: ipu7: add IPU7 firmware ABI headers bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 6/7] media: ipu7: add IPU7 input system device driver bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 7/7] media: ipu7: add Makefile and Kconfig for IPU7 bingbu.cao
2025-02-25 5:55 ` Bingbu Cao [this message]
2025-02-21 12:55 ` [RFC PATCH 0/7] Intel IPU7 PCI and input system device drivers Sakari Ailus
2025-04-09 20:23 ` Laurent Pinchart
2025-03-03 16:23 ` Bjorn Helgaas
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=1f46cbd1-384a-44f8-4ec1-414409ded771@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=hans@hansg.org \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stanislaw.gruszka@linux.intel.com \
/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