All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Chauhan, Shekhar" <shekhar.chauhan@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: lucas.demarchi@intel.com, rodrigo.vivi@intel.com
Subject: Re: [PATCH 3/3] drm/xe/pciids: separate ARL and MTL PCI IDs
Date: Thu, 05 Sep 2024 10:46:35 +0300	[thread overview]
Message-ID: <87mskmr19g.fsf@intel.com> (raw)
In-Reply-To: <3241416b-92d0-4ca2-9329-43ffee85819b@intel.com>

On Thu, 05 Sep 2024, "Chauhan, Shekhar" <shekhar.chauhan@intel.com> wrote:
> On 9/4/2024 3:16 PM, 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>
>> ---
>>   drivers/gpu/drm/xe/xe_pci.c   |  1 +
>>   include/drm/intel/xe_pciids.h | 13 ++++++++-----
>>   2 files changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
>> index b1cf21d77def..5c5eef2ae725 100644
>> --- a/drivers/gpu/drm/xe/xe_pci.c
>> +++ b/drivers/gpu/drm/xe/xe_pci.c
>> @@ -394,6 +394,7 @@ static const struct pci_device_id pciidlist[] = {
>>   	XE_ATS_M_IDS(INTEL_VGA_DEVICE, &ats_m_desc),
>>   	XE_DG2_IDS(INTEL_VGA_DEVICE, &dg2_desc),
>>   	XE_PVC_IDS(INTEL_VGA_DEVICE, &pvc_desc),
>> +	XE_ARL_IDS(INTEL_VGA_DEVICE, &mtl_desc),
> With this approach of segregating PCI IDs of two platforms, wouldn't it 
> make more sense to have two separate platform descriptors as well, say, 
> mtl_desc and a new one "arl_desc"?

Not if they are exactly the same.

>>   	XE_MTL_IDS(INTEL_VGA_DEVICE, &mtl_desc),
>>   	XE_LNL_IDS(INTEL_VGA_DEVICE, &lnl_desc),
>>   	XE_BMG_IDS(INTEL_VGA_DEVICE, &bmg_desc),
>> diff --git a/include/drm/intel/xe_pciids.h b/include/drm/intel/xe_pciids.h
>> index 334ab02ed6ca..67baa7c2246a 100644
>> --- a/include/drm/intel/xe_pciids.h
>> +++ b/include/drm/intel/xe_pciids.h
>> @@ -176,16 +176,19 @@
>>   	XE_ATS_M150_IDS(MACRO__, ## __VA_ARGS__),\
>>   	XE_ATS_M75_IDS(MACRO__, ## __VA_ARGS__)
>>   
>> -/* MTL / ARL */
>> +/* ARL */
>> +#define XE_ARL_IDS(MACRO__, ...)		\
>> +	MACRO__(0x7D41, ## __VA_ARGS__),	\
>> +	MACRO__(0x7D51, ## __VA_ARGS__),        \
>> +	MACRO__(0x7D67, ## __VA_ARGS__),	\
>> +	MACRO__(0x7DD1, ## __VA_ARGS__)
>> +
> Also, if we're following platform public release timelines, can we have 
> MTL block of PCI IDs above the ARL block?

Can do if it matters.

BR,
Jani.

>> +/* MTL */
>>   #define XE_MTL_IDS(MACRO__, ...)		\
>>   	MACRO__(0x7D40, ## __VA_ARGS__),	\
>> -	MACRO__(0x7D41, ## __VA_ARGS__),	\
>>   	MACRO__(0x7D45, ## __VA_ARGS__),	\
>> -	MACRO__(0x7D51, ## __VA_ARGS__),        \
>>   	MACRO__(0x7D55, ## __VA_ARGS__),	\
>>   	MACRO__(0x7D60, ## __VA_ARGS__),	\
>> -	MACRO__(0x7D67, ## __VA_ARGS__),	\
>> -	MACRO__(0x7DD1, ## __VA_ARGS__),        \
>>   	MACRO__(0x7DD5, ## __VA_ARGS__)
>>   
>>   /* PVC */

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-09-05  7:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  9:46 [PATCH 0/3] drm/xe/pciids: more ADL-N, cleanups Jani Nikula
2024-09-04  9:46 ` [PATCH 1/3] drm/xe/pciids: add some missing ADL-N PCI IDs Jani Nikula
2024-09-05  5:50   ` Pottumuttu, Sai Teja
2024-09-06 12:43     ` Jani Nikula
2024-09-04  9:46 ` [PATCH 2/3] drm/xe/pciids: separate RPL-U and RPL-P " Jani Nikula
2024-09-05  5:56   ` Pottumuttu, Sai Teja
2024-09-04  9:46 ` [PATCH 3/3] drm/xe/pciids: separate ARL and MTL " Jani Nikula
2024-09-05  6:05   ` Chauhan, Shekhar
2024-09-05  7:46     ` Jani Nikula [this message]
2024-09-05 10:09       ` Chauhan, Shekhar
2024-09-04  9:54 ` ✓ CI.Patch_applied: success for drm/xe/pciids: more ADL-N, cleanups Patchwork
2024-09-04  9:55 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-04  9:57 ` ✓ CI.KUnit: success " Patchwork
2024-09-04 10:11 ` ✓ CI.Build: " Patchwork
2024-09-04 10:13 ` ✓ CI.Hooks: " Patchwork
2024-09-04 10:14 ` ✓ CI.checksparse: " Patchwork
2024-09-04 10:52 ` ✓ CI.BAT: " Patchwork
2024-09-04 12:41 ` ✗ CI.FULL: 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=87mskmr19g.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=shekhar.chauhan@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.