All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH] drm/i915: Force compilation with intel-iommu for CI validation
Date: Tue, 10 Sep 2019 15:23:39 +0100	[thread overview]
Message-ID: <20190910142339.17072-1-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <20190910134417.14085-1-chris@chris-wilson.co.uk>

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 drivers/gpu/drm/i915/Kconfig.debug | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/gpu/drm/i915/Kconfig.debug b/drivers/gpu/drm/i915/Kconfig.debug
index 00786a142ff0..c5c00cad6ba1 100644
--- a/drivers/gpu/drm/i915/Kconfig.debug
+++ b/drivers/gpu/drm/i915/Kconfig.debug
@@ -20,6 +20,13 @@ config DRM_I915_WERROR
 config DRM_I915_DEBUG
         bool "Enable additional driver debugging"
         depends on DRM_I915
+	select PCI_MSI
+	select IOMMU_API
+	select IOMMU_IOVA
+	select NEED_DMA_MAP_STATE
+	select DMAR_TABLE
+	select INTEL_IOMMU
+	select INTEL_IOMMU_DEFAULT_ON
         select DEBUG_FS
         select PREEMPT_COUNT
         select REFCOUNT_FULL
-- 
2.23.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-09-10 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 13:44 [CI 1/3] drm/i915: Force compilation with intel-iommu for CI validation Chris Wilson
2019-09-10 13:44 ` [CI 2/3] iommu/intel: Declare Broadwell igfx dmar support snafu Chris Wilson
2019-09-10 13:44 ` [CI 3/3] iommu/intel: Ignore igfx_off Chris Wilson
2019-09-10 14:23 ` Chris Wilson [this message]
2019-09-10 14:29 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with drm/i915: Force compilation with intel-iommu for CI validation (rev2) Patchwork
2019-09-10 15:04 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-10 22:13 ` ✓ Fi.CI.IGT: " 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=20190910142339.17072-1-chris@chris-wilson.co.uk \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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 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.