From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ravi Kumar Vodapalli <ravi.kumar.vodapalli@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: balasubramani.vivekanandan@intel.com, matthew.d.roper@intel.com,
lucas.demarchi@intel.com, gustavo.sousa@intel.com,
radhakrishna.sripada@intel.com, clinton.a.taylor@intel.com,
matthew.s.atwood@intel.com, dnyaneshwar.bhadane@intel.com,
haridhar.kalvala@intel.com, shekhar.chauhan@intel.com
Subject: Re: [PATCH] drm/i915: Add new pciid's to DG2 platform
Date: Tue, 26 Mar 2024 11:55:46 +0200 [thread overview]
Message-ID: <8734sdiafx.fsf@intel.com> (raw)
In-Reply-To: <20240326094820.3828528-1-ravi.kumar.vodapalli@intel.com>
On Tue, 26 Mar 2024, Ravi Kumar Vodapalli <ravi.kumar.vodapalli@intel.com> wrote:
> New pciid's are added in Bspec for DG2 platform
drm/i915 subject prefix does not match the patch, which is for xe.
Do the i915 PCI IDs also need updating?
And please call them PCI IDs instead of "pciid's".
BR,
Jani.
>
> Bspec: 44477
> Signed-off-by: Ravi Kumar Vodapalli <ravi.kumar.vodapalli@intel.com>
> ---
> include/drm/xe_pciids.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h
> index ab4a8987ac65..c7fc288dacee 100644
> --- a/include/drm/xe_pciids.h
> +++ b/include/drm/xe_pciids.h
> @@ -134,7 +134,9 @@
> MACRO__(0x5692, ## __VA_ARGS__), \
> MACRO__(0x56A0, ## __VA_ARGS__), \
> MACRO__(0x56A1, ## __VA_ARGS__), \
> - MACRO__(0x56A2, ## __VA_ARGS__)
> + MACRO__(0x56A2, ## __VA_ARGS__), \
> + MACRO__(0x56BE, ## __VA_ARGS__), \
> + MACRO__(0x56BF, ## __VA_ARGS__)
>
> #define XE_DG2_G11_IDS(MACRO__, ...) \
> MACRO__(0x5693, ## __VA_ARGS__), \
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-03-26 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 9:48 [PATCH] drm/i915: Add new pciid's to DG2 platform Ravi Kumar Vodapalli
2024-03-26 9:55 ` Jani Nikula [this message]
2024-03-27 0:05 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-03-27 0:16 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-27 15:42 ` ✗ Fi.CI.IGT: 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=8734sdiafx.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=haridhar.kalvala@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=matthew.s.atwood@intel.com \
--cc=radhakrishna.sripada@intel.com \
--cc=ravi.kumar.vodapalli@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.