Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Pottumuttu, Sai Teja" <sai.teja.pottumuttu@intel.com>,
	Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/pciid: Add new PCI id for ARL
Date: Tue, 10 Sep 2024 13:21:21 +0300	[thread overview]
Message-ID: <87ttenkdwe.fsf@intel.com> (raw)
In-Reply-To: <8f854bba-c78e-4c81-a78d-04b385ff4641@intel.com>

On Tue, 10 Sep 2024, "Pottumuttu, Sai Teja" <sai.teja.pottumuttu@intel.com> wrote:
> On 10-09-2024 11:53, Dnyaneshwar Bhadane wrote:
>> Add new PCI id for ARL platform.
>>
>> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>
> I assume that you would send another patch to sync this PCI ID addition 
> in xe_pciids.h as well

Yes, preferrably send both at the same time, even though one is to be
merged to drm-intel-next and the other to drm-xe-next. We don't want the
PCI IDs to be out of sync.

Lucas, Rodrigo, another reason for [1].

BR,
Jani.


[1] https://lore.kernel.org/r/5e703ab69846d519335f3e7f5bcf84ff1704cd09.1725297097.git.jani.nikula@intel.com


>
> With that,
>
> Reviewed-by: Sai Teja Pottumuttu <sai.teja.pottumuttu@intel.com>
>
>> ---
>>   include/drm/intel/i915_pciids.h | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/drm/intel/i915_pciids.h b/include/drm/intel/i915_pciids.h
>> index cbb12fdbcb7f..02156c6f79b6 100644
>> --- a/include/drm/intel/i915_pciids.h
>> +++ b/include/drm/intel/i915_pciids.h
>> @@ -769,7 +769,8 @@
>>   	MACRO__(0x7D41, ## __VA_ARGS__), \
>>   	MACRO__(0x7D51, ## __VA_ARGS__), \
>>   	MACRO__(0x7D67, ## __VA_ARGS__), \
>> -	MACRO__(0x7DD1, ## __VA_ARGS__)
>> +	MACRO__(0x7DD1, ## __VA_ARGS__), \
>> +	MACRO__(0xB640, ## __VA_ARGS__)
>>   
>>   /* MTL */
>>   #define INTEL_MTL_IDS(MACRO__, ...) \

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-09-10 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  6:23 [PATCH] drm/i915/pciid: Add new PCI id for ARL Dnyaneshwar Bhadane
2024-09-10  7:46 ` Garg, Nemesa
2024-09-10  7:59 ` Pottumuttu, Sai Teja
2024-09-10 10:21   ` Jani Nikula [this message]
2024-09-10 13:02 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-09-11  6:40 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-20 20:37   ` Matt Roper

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=87ttenkdwe.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sai.teja.pottumuttu@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