From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <lucas.demarchi@intel.com>
Subject: Re: [PATCH 2/2] drm/i915/pciids: separate ARL and MTL PCI IDs
Date: Thu, 5 Sep 2024 13:15:10 -0400 [thread overview]
Message-ID: <ZtnnHsMJGGKOmwqJ@intel.com> (raw)
In-Reply-To: <b70af19ea017a76af4678d0a4ee8332253ee1f3b.1725443418.git.jani.nikula@intel.com>
On Wed, Sep 04, 2024 at 12:51:33PM +0300, Jani Nikula wrote:
> Avoid including PCI IDs for one platform to the PCI IDs of another. It's
> more clear to deal with them completely separately at the PCI ID macro
> level.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_device.c | 1 +
> drivers/gpu/drm/i915/i915_pci.c | 1 +
> include/drm/intel/i915_pciids.h | 4 ++--
> 3 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_device.c b/drivers/gpu/drm/i915/display/intel_display_device.c
> index 1b46ba985580..408c76852495 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_device.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_device.c
> @@ -1318,6 +1318,7 @@ static const struct {
> INTEL_RPLU_IDS(INTEL_DISPLAY_DEVICE, &adl_p_desc),
> INTEL_RPLP_IDS(INTEL_DISPLAY_DEVICE, &adl_p_desc),
> INTEL_DG2_IDS(INTEL_DISPLAY_DEVICE, &dg2_desc),
> + INTEL_ARL_IDS(INTEL_DISPLAY_DEVICE, &mtl_desc),
> INTEL_MTL_IDS(INTEL_DISPLAY_DEVICE, &mtl_desc),
> INTEL_LNL_IDS(INTEL_DISPLAY_DEVICE, &lnl_desc),
> INTEL_BMG_IDS(INTEL_DISPLAY_DEVICE, &bmg_desc),
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index d37bb3a704d0..617f411feb8c 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -870,6 +870,7 @@ static const struct pci_device_id pciidlist[] = {
> INTEL_RPLP_IDS(INTEL_VGA_DEVICE, &adl_p_info),
> INTEL_DG2_IDS(INTEL_VGA_DEVICE, &dg2_info),
> INTEL_ATS_M_IDS(INTEL_VGA_DEVICE, &ats_m_info),
> + INTEL_ARL_IDS(INTEL_VGA_DEVICE, &mtl_info),
> INTEL_MTL_IDS(INTEL_VGA_DEVICE, &mtl_info),
> {}
> };
> diff --git a/include/drm/intel/i915_pciids.h b/include/drm/intel/i915_pciids.h
> index 6a78df5687c5..cbb12fdbcb7f 100644
> --- a/include/drm/intel/i915_pciids.h
> +++ b/include/drm/intel/i915_pciids.h
> @@ -764,15 +764,15 @@
> INTEL_ATS_M150_IDS(MACRO__, ## __VA_ARGS__), \
> INTEL_ATS_M75_IDS(MACRO__, ## __VA_ARGS__)
>
> -/* MTL */
> +/* ARL */
> #define INTEL_ARL_IDS(MACRO__, ...) \
> MACRO__(0x7D41, ## __VA_ARGS__), \
> MACRO__(0x7D51, ## __VA_ARGS__), \
> MACRO__(0x7D67, ## __VA_ARGS__), \
> MACRO__(0x7DD1, ## __VA_ARGS__)
>
> +/* MTL */
> #define INTEL_MTL_IDS(MACRO__, ...) \
> - INTEL_ARL_IDS(MACRO__, ## __VA_ARGS__), \
> MACRO__(0x7D40, ## __VA_ARGS__), \
> MACRO__(0x7D45, ## __VA_ARGS__), \
> MACRO__(0x7D55, ## __VA_ARGS__), \
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-09-05 17:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 9:51 [PATCH 0/2] drm/i915/pciids: cleanups Jani Nikula
2024-09-04 9:51 ` [PATCH 1/2] drm/i915/pciids: use designated initializers in INTEL_VGA_DEVICE() Jani Nikula
2024-09-04 10:24 ` Jani Nikula
2024-09-05 17:14 ` Rodrigo Vivi
2024-09-05 18:02 ` Jani Nikula
2024-09-04 9:51 ` [PATCH 2/2] drm/i915/pciids: separate ARL and MTL PCI IDs Jani Nikula
2024-09-05 17:15 ` Rodrigo Vivi [this message]
2024-09-04 10:58 ` ✓ CI.Patch_applied: success for drm/i915/pciids: cleanups Patchwork
2024-09-04 10:58 ` ✓ CI.checkpatch: " Patchwork
2024-09-04 11:00 ` ✓ CI.KUnit: " Patchwork
2024-09-04 11:18 ` ✓ CI.Build: " Patchwork
2024-09-04 11:20 ` ✓ CI.Hooks: " Patchwork
2024-09-04 11:21 ` ✗ CI.checksparse: warning " Patchwork
2024-09-05 11:15 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-05 11:16 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-06 10:22 ` ✓ CI.FULL: " Patchwork
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=ZtnnHsMJGGKOmwqJ@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@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.