Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 0/3] i915: Upstream initial DG2 PCI IDs
Date: Mon, 25 Apr 2022 14:12:48 -0700	[thread overview]
Message-ID: <20220425211251.77154-1-matthew.d.roper@intel.com> (raw)

We've had all of our DG2 and ATS-M PCI IDs in the topic/core-for-CI
branch for a while, but we've now got the critical uapi changes in place
to unblock upstreaming the initial subset (which correspond to
"motherboard down" designs) through the drm-intel tree.  The remaining
IDs (which correspond to add-in card designs) will remain in the
topic/core-for-CI branch until some additional prerequisite
functionality lands.

Since the topic/core-for-CI branch is a rebasing branch, we'll just
rebase the relevant IDs out of it when the time comes, but I'm sending
them as a formal revert here so that the CI system doesn't get confused
when testing the series.

Note that a handful of new DG2-G12 IDs have also shown up recently, so
those additional IDs are also included here.

Cc: Lucas De Marchi <lucas.demarchi@intel.com>

Matt Roper (3):
  topic/core-for-CI:  Revert DG2 and ATS-M device IDs
  drm/i915: Add first set of DG2 PCI IDs
  topic/core-for-CI: Add remaining DG2 and ATS-M device IDs

 include/drm/i915_pciids.h | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.35.1


             reply	other threads:[~2022-04-25 21:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 21:12 Matt Roper [this message]
2022-04-25 21:12 ` [Intel-gfx] [PATCH v2 1/3] topic/core-for-CI: Revert DG2 and ATS-M device IDs Matt Roper
2022-04-25 21:12 ` [Intel-gfx] [PATCH v2 2/3] drm/i915: Add first set of DG2 PCI IDs Matt Roper
2022-04-27  7:01   ` Lucas De Marchi
2022-04-25 21:12 ` [Intel-gfx] [PATCH v2 3/3] topic/core-for-CI: Add remaining DG2 and ATS-M device IDs Matt Roper
2022-04-25 21:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: Upstream initial DG2 PCI IDs Patchwork
2022-04-25 21:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-25 22:20   ` Matt Roper
2022-04-26  0:07     ` Vudum, Lakshminarayana
2022-04-25 22:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-26  0:17 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-26 17:06   ` Matt Roper
2022-04-27  5:05     ` Vudum, Lakshminarayana
2022-04-27  4:36 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-04-27  4:53 ` Patchwork
2022-04-28  0:24   ` 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=20220425211251.77154-1-matthew.d.roper@intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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