From: Alexander Usyskin <alexander.usyskin@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Alexander Usyskin <alexander.usyskin@intel.com>,
linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>
Subject: [Intel-gfx] [PATCH v5 14/14] HAX: drm/i915: force INTEL_MEI_GSC on for CI
Date: Wed, 6 Jul 2022 14:43:45 +0300 [thread overview]
Message-ID: <20220706114345.1128018-15-alexander.usyskin@intel.com> (raw)
In-Reply-To: <20220706114345.1128018-1-alexander.usyskin@intel.com>
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
After the new config option is merged we'll enable it by default in the
CI config, but for now just force it on via the i915 Kconfig so we can
get pre-merge CI results for it.
Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
---
drivers/gpu/drm/i915/Kconfig.debug | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/Kconfig.debug b/drivers/gpu/drm/i915/Kconfig.debug
index e7fd3e76f8a2..be4ef485d6c1 100644
--- a/drivers/gpu/drm/i915/Kconfig.debug
+++ b/drivers/gpu/drm/i915/Kconfig.debug
@@ -48,6 +48,7 @@ config DRM_I915_DEBUG
select DRM_I915_DEBUG_RUNTIME_PM
select DRM_I915_SW_FENCE_DEBUG_OBJECTS
select DRM_I915_SELFTEST
+ select INTEL_MEI_GSC
select BROKEN # for prototype uAPI
default n
help
--
2.34.1
next prev parent reply other threads:[~2022-07-06 11:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 11:43 [Intel-gfx] [PATCH v5 00/14] GSC support for XeHP SDV and DG2 platforms Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 01/14] drm/i915/gsc: skip irq initialization if using polling Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 02/14] drm/i915/gsc: add slow_fw flag to the mei auxiliary device Alexander Usyskin
2022-07-07 15:21 ` Rodrigo Vivi
2022-07-18 13:47 ` Winkler, Tomas
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 03/14] drm/i915/gsc: add slow_fw flag to the gsc device definition Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 04/14] drm/i915/gsc: add GSC XeHP SDV platform definition Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 05/14] mei: gsc: use polling instead of interrupts Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 06/14] mei: gsc: wait for reset thread on stop Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 07/14] mei: extend timeouts on slow devices Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 08/14] mei: bus: export common mkhi definitions into a separate header Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 09/14] mei: mkhi: add memory ready command Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 10/14] mei: gsc: setup gsc extended operational memory Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 11/14] mei: gsc: add transition to PXP mode in resume flow Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 12/14] mei: debugfs: add pxp mode to devstate in debugfs Alexander Usyskin
2022-07-06 11:43 ` [Intel-gfx] [PATCH v5 13/14] drm/i915/gsc: allocate extended operational memory in LMEM Alexander Usyskin
2022-08-02 17:29 ` [Intel-gfx] [v5, " Teres Alexis, Alan Previn
2022-08-02 18:49 ` Winkler, Tomas
2022-07-06 11:43 ` Alexander Usyskin [this message]
2022-07-06 12:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for GSC support for XeHP SDV and DG2 platforms (rev5) Patchwork
2022-07-06 12:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-07-06 12:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-06 17:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-08 13:34 ` [Intel-gfx] [PATCH v5 00/14] GSC support for XeHP SDV and DG2 platforms Greg Kroah-Hartman
2022-07-08 13:57 ` Rodrigo Vivi
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=20220706114345.1128018-15-alexander.usyskin@intel.com \
--to=alexander.usyskin@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tomas.winkler@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=vitaly.lubart@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