Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Ravi Kumar Vodapalli <ravi.kumar.vodapalli@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: balasubramani.vivekanandan@intel.com, Vodapalli@freedesktop.org
Subject: Re: [PATCH] drm/xe/bmg: Add one additional PCI ID
Date: Fri, 4 Jul 2025 13:04:47 +0100	[thread overview]
Message-ID: <1653febe-2dce-4c1b-9c70-97dcdc1b17fa@intel.com> (raw)
In-Reply-To: <20250704103527.100178-1-ravi.kumar.vodapalli@intel.com>

On 04/07/2025 11:35, Ravi Kumar Vodapalli wrote:
> From: "Vodapalli, Ravi Kumar" <ravi.kumar.vodapalli@intel.com>
> 
> One additional PCI ID is added in Bspec for BMG, Add it so that
> driver recognizes this device with this new ID.
> 
> Bspec: 68090
> Signed-off-by: Vodapalli, Ravi Kumar <ravi.kumar.vodapalli@intel.com>

Going by similar changes should we also add:

Cc: stable@vger.kernel.org # v6.12+

?

That way user doesn't need a bleeding edge kernel just to get a working 
machine, or is there something special about this pciid which needs some 
other kernel changes?

> ---
>   include/drm/intel/pciids.h | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/include/drm/intel/pciids.h b/include/drm/intel/pciids.h
> index a0180d10e260..76f8d26f9cc9 100644
> --- a/include/drm/intel/pciids.h
> +++ b/include/drm/intel/pciids.h
> @@ -846,6 +846,7 @@
>   /* BMG */
>   #define INTEL_BMG_IDS(MACRO__, ...) \
>   	MACRO__(0xE202, ## __VA_ARGS__), \
> +	MACRO__(0xE209, ## __VA_ARGS__), \
>   	MACRO__(0xE20B, ## __VA_ARGS__), \
>   	MACRO__(0xE20C, ## __VA_ARGS__), \
>   	MACRO__(0xE20D, ## __VA_ARGS__), \


  parent reply	other threads:[~2025-07-04 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04 10:35 [PATCH] drm/xe/bmg: Add one additional PCI ID Ravi Kumar Vodapalli
2025-07-04 10:42 ` ✓ CI.KUnit: success for drm/xe/bmg: Add one additional PCI ID (rev2) Patchwork
2025-07-04 10:48 ` [PATCH] drm/xe/bmg: Add one additional PCI ID Shekhar Chauhan
2025-07-04 12:04 ` Matthew Auld [this message]
2025-07-04 13:16   ` Vodapalli, Ravi Kumar
  -- strict thread matches above, loose matches on Subject: below --
2025-03-25 22:47 Matt Roper
2025-03-25 23:25 ` Taylor, Clinton A
2025-03-26  4:30 ` Lucas De Marchi

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=1653febe-2dce-4c1b-9c70-97dcdc1b17fa@intel.com \
    --to=matthew.auld@intel.com \
    --cc=Vodapalli@freedesktop.org \
    --cc=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ravi.kumar.vodapalli@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