From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
laurent.pinchart@ideasonboard.com, phasta@mailbox.org,
helgaas@kernel.org, jerry.w.hu@intel.com, hao.yao@intel.com,
tian.shu.qiu@intel.com, bingbu.cao@linux.intel.com
Subject: Re: [PATCH 1/8] media: Rename the IPU PCI device table header and add IPU7 PCI IDs
Date: Tue, 29 Apr 2025 09:57:51 +0200 [thread overview]
Message-ID: <aBCGf66Wy2+kU3nl@linux.intel.com> (raw)
In-Reply-To: <20250429032841.115107-2-bingbu.cao@intel.com>
On Tue, Apr 29, 2025 at 11:28:34AM +0800, bingbu.cao@intel.com wrote:
> From: Bingbu Cao <bingbu.cao@intel.com>
>
> Rename the IPU PCI device table header file and add the IPU7 PCI device
> IDs.
>
> Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> ---
> drivers/media/pci/intel/ipu6/ipu6.c | 2 +-
> .../media/{ipu6-pci-table.h => ipu-pci-table.h} | 14 +++++++++++---
> 2 files changed, 12 insertions(+), 4 deletions(-)
> rename include/media/{ipu6-pci-table.h => ipu-pci-table.h} (68%)
>
> diff --git a/drivers/media/pci/intel/ipu6/ipu6.c b/drivers/media/pci/intel/ipu6/ipu6.c
> index 277af7cda8ee..aa859220ba94 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6.c
> @@ -21,7 +21,7 @@
> #include <linux/types.h>
>
> #include <media/ipu-bridge.h>
> -#include <media/ipu6-pci-table.h>
> +#include <media/ipu-pci-table.h>
>
> #include "ipu6.h"
> #include "ipu6-bus.h"
> diff --git a/include/media/ipu6-pci-table.h b/include/media/ipu-pci-table.h
> similarity index 68%
> rename from include/media/ipu6-pci-table.h
> rename to include/media/ipu-pci-table.h
> index 0899d9d2f978..528080c6f742 100644
> --- a/include/media/ipu6-pci-table.h
> +++ b/include/media/ipu-pci-table.h
> @@ -3,8 +3,8 @@
> * Copyright (C) 2024 Intel Corporation
> */
>
> -#ifndef __IPU6_PCI_TBL_H__
> -#define __IPU6_PCI_TBL_H__
> +#ifndef __IPU_PCI_TBL_H__
> +#define __IPU_PCI_TBL_H__
>
> #include <linux/pci.h>
>
> @@ -15,6 +15,9 @@
> #define PCI_DEVICE_ID_INTEL_IPU6EP_RPLP 0xa75d
> #define PCI_DEVICE_ID_INTEL_IPU6EP_MTL 0x7d19
>
> +#define PCI_DEVICE_ID_INTEL_IPU7_PCI_ID 0x645d
> +#define PCI_DEVICE_ID_INTEL_IPU7P5_PCI_ID 0xb05d
> +
> static const struct pci_device_id ipu6_pci_tbl[] = {
> { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6) },
> { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6SE) },
> @@ -25,4 +28,9 @@ static const struct pci_device_id ipu6_pci_tbl[] = {
> { }
> };
>
> -#endif /* __IPU6_PCI_TBL_H__ */
> +static const struct pci_device_id ipu7_pci_tbl[] = {
> + {PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU7_PCI_ID)},
> + {PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU7P5_PCI_ID)},
> + { }
> +};
> +#endif /* __IPU_PCI_TBL_H__ */
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-04-29 7:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 3:28 [PATCH 0/8] Intel IPU7 PCI and input system device drivers bingbu.cao
2025-04-29 3:28 ` [PATCH 1/8] media: Rename the IPU PCI device table header and add IPU7 PCI IDs bingbu.cao
2025-04-29 7:57 ` Stanislaw Gruszka [this message]
2025-04-29 3:28 ` [PATCH 2/8] media: staging/ipu7: add Intel IPU7 PCI device driver bingbu.cao
2025-04-29 9:46 ` Stanislaw Gruszka
2025-04-29 3:28 ` [PATCH 3/8] media: staging/ipu7: add IPU7 DMA APIs and MMU mapping bingbu.cao
2025-04-29 3:28 ` [PATCH 4/8] media: staging/ipu7: add firmware parse, syscom interface and boot bingbu.cao
2025-04-29 3:28 ` [PATCH 5/8] media: staging/ipu7: add IPU7 firmware ABI headers bingbu.cao
2025-04-29 6:39 ` Sakari Ailus
2025-04-29 3:28 ` [PATCH 6/8] media: staging/ipu7: add IPU7 input system device driver bingbu.cao
2025-04-29 7:53 ` Stanislaw Gruszka
2025-04-29 8:24 ` Sakari Ailus
2025-05-26 6:52 ` Bingbu Cao
2025-05-26 7:56 ` Sakari Ailus
2025-04-29 3:28 ` [PATCH 7/8] media: staging/ipu7: add Makefile and Kconfig for IPU7 bingbu.cao
2025-04-29 3:28 ` [PATCH 8/8] MAINTAINERS: add maintainers for Intel IPU7 input system driver bingbu.cao
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=aBCGf66Wy2+kU3nl@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=hao.yao@intel.com \
--cc=helgaas@kernel.org \
--cc=jerry.w.hu@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=phasta@mailbox.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.