From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, lucas.demarchi@intel.com
Subject: Re: [PATCH 0/8] drm/i915 & drm/xe: shared PCI ID macros
Date: Wed, 04 Sep 2024 12:55:54 +0300 [thread overview]
Message-ID: <87le07spxx.fsf@intel.com> (raw)
In-Reply-To: <cover.1725297097.git.jani.nikula@intel.com>
On Mon, 02 Sep 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> There's considerable overlap in i915 and xe PCI ID macros, and (as can
> be seen in this series) they get updated out of sync. With i915 display
> continuing to use PCI IDs for platforms that i915 core does not support,
> but xe does, the duplication will just increase. Just use a single file
> for all of them.
>
> BR,
> Jani.
>
> Jani Nikula (8):
> drm/i915/pciids: use designated initializers in INTEL_VGA_DEVICE()
> drm/i915/pciids: separate ARL and MTL PCI IDs
Sent these for drm-intel-next:
https://lore.kernel.org/r/cover.1725443418.git.jani.nikula@intel.com
> drm/xe/pciids: add some missing ADL-N PCI IDs
> drm/xe/pciids: separate RPL-U and RPL-P PCI IDs
> drm/xe/pciids: separate ARL and MTL PCI IDs
Sent these for drm-xe-next:
https://lore.kernel.org/r/cover.1725443121.git.jani.nikula@intel.com
> drm/i915/pciids: add PVC PCI ID macros
> drm/intel/pciids: rename i915_pciids.h to just pciids.h
> drm/xe: switch to common PCI ID macros
Dropping these for now, but I might resurrect the idea after the merge
window.
BR,
Jani.
>
> arch/x86/kernel/early-quirks.c | 2 +-
> .../drm/i915/display/intel_display_device.c | 3 +-
> drivers/gpu/drm/i915/i915_pci.c | 3 +-
> drivers/gpu/drm/i915/intel_device_info.c | 2 +-
> drivers/gpu/drm/xe/xe_pci.c | 49 ++--
> include/drm/intel/{i915_pciids.h => pciids.h} | 63 ++---
> include/drm/intel/xe_pciids.h | 218 ------------------
> 7 files changed, 64 insertions(+), 276 deletions(-)
> rename include/drm/intel/{i915_pciids.h => pciids.h} (96%)
> delete mode 100644 include/drm/intel/xe_pciids.h
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-09-04 9:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 17:13 [PATCH 0/8] drm/i915 & drm/xe: shared PCI ID macros Jani Nikula
2024-09-02 17:14 ` [PATCH 1/8] drm/i915/pciids: use designated initializers in INTEL_VGA_DEVICE() Jani Nikula
2024-09-02 17:14 ` [PATCH 2/8] drm/i915/pciids: separate ARL and MTL PCI IDs Jani Nikula
2024-09-02 17:14 ` [PATCH 3/8] drm/xe/pciids: add some missing ADL-N " Jani Nikula
2024-09-02 17:14 ` [PATCH 4/8] drm/xe/pciids: separate RPL-U and RPL-P " Jani Nikula
2024-09-02 17:14 ` [PATCH 5/8] drm/xe/pciids: separate ARL and MTL " Jani Nikula
2024-09-02 17:14 ` [PATCH 6/8] drm/i915/pciids: add PVC PCI ID macros Jani Nikula
2024-09-02 17:14 ` [PATCH 7/8] drm/intel/pciids: rename i915_pciids.h to just pciids.h Jani Nikula
2024-09-10 18:52 ` Rodrigo Vivi
2024-09-02 17:14 ` [PATCH 8/8] drm/xe: switch to common PCI ID macros Jani Nikula
2024-09-10 18:53 ` Rodrigo Vivi
2024-09-02 18:14 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915 & drm/xe: shared " Patchwork
2024-09-02 18:14 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-02 18:33 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-03 2:41 ` [PATCH 0/8] " Lucas De Marchi
2024-09-03 7:32 ` Jani Nikula
2024-09-10 15:04 ` Lucas De Marchi
2024-09-03 20:39 ` ✓ Fi.CI.IGT: success for " Patchwork
2024-09-04 9:55 ` Jani Nikula [this message]
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=87le07spxx.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).