Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anusha Srivatsa <anusha.srivatsa@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
Subject: [Intel-xe] [PATCH 0/5] Add Raptorlake Support
Date: Tue,  3 Oct 2023 13:37:11 -0700	[thread overview]
Message-ID: <20231003203716.108979-1-anusha.srivatsa@intel.com> (raw)

Keep the naming convention consistent with i915.
As part of it making some consistent naming changes
so we can continue to use some macro magic moving forward.
It does make the name bigger - ALDERLAKE instead of
just ADL. But this way the platform name is ALDERLAKE_P
everywhere which is easier to remember and use.(previosuly
the driver had ADLP_ usages for some defines - like ADLP_RPLU_* etc)

While at it also adding some missing support in kunit for the
some subplatforms.

v2: Split any changes to xe/compat-i915-headers/i915_drv.h file
as a separate patch, regardless of build failures at that point.

v3: Add fixup! to patches to make merging easier

Anusha Srivatsa (5):
  drm/xe/rplu: s/ADLP/ALDERLAKE_P
  fixup! drm/xe/rplu: s/ADLP/ALDERLAKE_P
  drm/xe/rpls: Add RPLS Support
  drm/xe/rpls: Add Stepping info for RPLS
  drm/xe: Add missing ADL entries to xe_test_wa

 drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h |  2 +-
 drivers/gpu/drm/xe/tests/xe_wa_test.c             |  2 ++
 drivers/gpu/drm/xe/xe_pci.c                       |  9 ++++++++-
 drivers/gpu/drm/xe/xe_platform_types.h            |  3 ++-
 drivers/gpu/drm/xe/xe_step.c                      | 10 +++++++++-
 5 files changed, 22 insertions(+), 4 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-10-03 20:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 20:37 Anusha Srivatsa [this message]
2023-10-03 20:37 ` [Intel-xe] [PATCH 1/5] drm/xe/rplu: s/ADLP/ALDERLAKE_P Anusha Srivatsa
2023-10-04 18:12   ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 2/5] fixup! " Anusha Srivatsa
2023-10-04  7:58   ` Jani Nikula
2023-10-04 18:16     ` Lucas De Marchi
2023-10-05 18:41       ` Rodrigo Vivi
2023-10-06  7:39         ` Jani Nikula
2023-10-03 20:37 ` [Intel-xe] [PATCH 3/5] drm/xe/rpls: Add RPLS Support Anusha Srivatsa
2023-10-04 18:19   ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS Anusha Srivatsa
2023-10-04 18:20   ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 5/5] drm/xe: Add missing ADL entries to xe_test_wa Anusha Srivatsa
2023-10-04 18:20   ` Lucas De Marchi
2023-10-03 22:04 ` [Intel-xe] ✓ CI.Patch_applied: success for Add Raptorlake Support (rev3) Patchwork
2023-10-03 22:04 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-10-03 22:06 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-10-03 22:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 22:13 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 22:14 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 22:52 ` [Intel-xe] ✓ CI.BAT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-10-05 20:54 [Intel-xe] [PATCH 0/5] Add Raptorlake Support Anusha Srivatsa
2023-10-06 22:54 ` Lucas De Marchi
2023-09-29 20:16 Anusha Srivatsa

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=20231003203716.108979-1-anusha.srivatsa@intel.com \
    --to=anusha.srivatsa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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