From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, lucas.demarchi@intel.com,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/5] drm/i915: don't include CML PCI IDs in CFL
Date: Wed, 08 May 2024 14:45:10 +0300 [thread overview]
Message-ID: <87o79gjznd.fsf@intel.com> (raw)
In-Reply-To: <ZjtapMK6kadLqHCN@intel.com>
On Wed, 08 May 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, May 07, 2024 at 09:47:16AM -0400, Rodrigo Vivi wrote:
>> On Tue, May 07, 2024 at 03:56:48PM +0300, Jani Nikula wrote:
>> > It's confusing for INTEL_CFL_IDS() to include all CML PCI IDs. Even if
>> > we treat them the same in a lot of places, CML is a platform of its own,
>> > and the lists of PCI IDs should not conflate them.
>> >
>> > Cc: Bjorn Helgaas <bhelgaas@google.com>
>> > Cc: linux-pci@vger.kernel.org
>> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> > ---
>> > arch/x86/kernel/early-quirks.c | 1 +
>> > drivers/gpu/drm/i915/display/intel_display_device.c | 1 +
>> > include/drm/i915_pciids.h | 12 +++++++-----
>> > 3 files changed, 9 insertions(+), 5 deletions(-)
>> >
>> > diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
>> > index 59f4aefc6bc1..2e2d15be4025 100644
>> > --- a/arch/x86/kernel/early-quirks.c
>> > +++ b/arch/x86/kernel/early-quirks.c
>> > @@ -547,6 +547,7 @@ static const struct pci_device_id intel_early_ids[] __initconst = {
>> > INTEL_BXT_IDS(&gen9_early_ops),
>> > INTEL_KBL_IDS(&gen9_early_ops),
>> > INTEL_CFL_IDS(&gen9_early_ops),
>> > + INTEL_CML_IDS(&gen9_early_ops),
>> > INTEL_GLK_IDS(&gen9_early_ops),
>> > INTEL_CNL_IDS(&gen9_early_ops),
>> > INTEL_ICL_11_IDS(&gen11_early_ops),
>> > diff --git a/drivers/gpu/drm/i915/display/intel_display_device.c b/drivers/gpu/drm/i915/display/intel_display_device.c
>> > index 56a2e17d7d9e..3aa7d1cdd228 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_display_device.c
>> > +++ b/drivers/gpu/drm/i915/display/intel_display_device.c
>> > @@ -832,6 +832,7 @@ static const struct {
>> > INTEL_GLK_IDS(&glk_display),
>> > INTEL_KBL_IDS(&skl_display),
>> > INTEL_CFL_IDS(&skl_display),
>> > + INTEL_CML_IDS(&skl_display),
>> > INTEL_ICL_11_IDS(&icl_display),
>> > INTEL_EHL_IDS(&jsl_ehl_display),
>> > INTEL_JSL_IDS(&jsl_ehl_display),
>> > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
>> > index 85ce33ad6e26..5f52c504ffde 100644
>> > --- a/include/drm/i915_pciids.h
>> > +++ b/include/drm/i915_pciids.h
>> > @@ -472,6 +472,12 @@
>> > INTEL_VGA_DEVICE(0x9BCA, info), \
>> > INTEL_VGA_DEVICE(0x9BCC, info)
>> >
>> > +#define INTEL_CML_IDS(info) \
>> > + INTEL_CML_GT1_IDS(info), \
>> > + INTEL_CML_GT2_IDS(info), \
>> > + INTEL_CML_U_GT1_IDS(info), \
>> > + INTEL_CML_U_GT2_IDS(info)
>> > +
>> > #define INTEL_KBL_IDS(info) \
>> > INTEL_KBL_GT1_IDS(info), \
>> > INTEL_KBL_GT2_IDS(info), \
>> > @@ -535,11 +541,7 @@
>> > INTEL_WHL_U_GT1_IDS(info), \
>> > INTEL_WHL_U_GT2_IDS(info), \
>> > INTEL_WHL_U_GT3_IDS(info), \
>> > - INTEL_AML_CFL_GT2_IDS(info), \
>> > - INTEL_CML_GT1_IDS(info), \
>> > - INTEL_CML_GT2_IDS(info), \
>> > - INTEL_CML_U_GT1_IDS(info), \
>> > - INTEL_CML_U_GT2_IDS(info)
>> > + INTEL_AML_CFL_GT2_IDS(info)
>>
>> Why only CML and not AML and WHL as well?
>
> Why do we even have CML as a separate platform? The only difference
> I can see is is that we do allow_read_ctx_timestamp() for CML but
> not for CFL. Does that even make sense?
git blame tells me:
5f4ae2704d59 ("drm/i915: Identify Cometlake platform")
dbc7e72897a4 ("drm/i915/gt: Make the CTX_TIMESTAMP readable on !rcs")
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-05-08 11:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 12:56 [PATCH 0/5] drm/i915: PCI ID macro and subplatform changes Jani Nikula
2024-05-07 12:56 ` [PATCH 1/5] drm/i915: don't include CML PCI IDs in CFL Jani Nikula
2024-05-07 13:47 ` Rodrigo Vivi
2024-05-08 8:33 ` Jani Nikula
2024-05-08 12:38 ` Rodrigo Vivi
2024-05-08 10:57 ` Ville Syrjälä
2024-05-08 11:45 ` Jani Nikula [this message]
2024-05-08 12:01 ` Ville Syrjälä
2024-05-10 10:24 ` Jani Nikula
2024-05-10 10:34 ` Ville Syrjälä
2024-05-10 11:24 ` Jani Nikula
2024-05-07 12:56 ` [PATCH 2/5] drm/i915: don't include RPL-U PCI IDs in RPL-P Jani Nikula
2024-05-08 12:41 ` Rodrigo Vivi
2024-05-07 12:56 ` [PATCH 3/5] drm/i915: separate RPL-U from RPL-P Jani Nikula
2024-05-08 12:46 ` Rodrigo Vivi
2024-05-07 12:56 ` [PATCH 4/5] drm/i915: simplify ULT/ULX subplatform detection Jani Nikula
2024-05-08 12:51 ` Rodrigo Vivi
2024-05-08 13:01 ` Jani Nikula
2024-05-08 13:52 ` Rodrigo Vivi
2024-05-07 12:56 ` [PATCH 5/5] drm/i915: make the PCI ID macros more flexible Jani Nikula
2024-05-07 13:56 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: PCI ID macro and subplatform changes Patchwork
2024-05-07 13:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-05-07 14:13 ` ✗ Fi.CI.BAT: failure " 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=87o79gjznd.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=bhelgaas@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@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;
as well as URLs for NNTP newsgroup(s).