All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v8 1/8] drm/i915: Program RPCS for Broadwell
Date: Tue, 29 May 2018 20:16:11 +0100	[thread overview]
Message-ID: <20180529191618.19050-2-lionel.g.landwerlin@intel.com> (raw)
In-Reply-To: <20180529191618.19050-1-lionel.g.landwerlin@intel.com>

From: Chris Wilson <chris@chris-wilson.co.uk>

Currently we only configure the power gating for Skylake and above, but
the configuration should equally apply to Broadwell and Braswell. Even
though, there is not as much variation as for later generations, we want
to expose control over the configuration to userspace and may want to
opt out of the "always-enabled" setting.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
---
 drivers/gpu/drm/i915/intel_lrc.c | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
index 8a6058b4102f..05e069a5c836 100644
--- a/drivers/gpu/drm/i915/intel_lrc.c
+++ b/drivers/gpu/drm/i915/intel_lrc.c
@@ -2517,13 +2517,6 @@ make_rpcs(struct drm_i915_private *dev_priv)
 {
 	u32 rpcs = 0;
 
-	/*
-	 * No explicit RPCS request is needed to ensure full
-	 * slice/subslice/EU enablement prior to Gen9.
-	*/
-	if (INTEL_GEN(dev_priv) < 9)
-		return 0;
-
 	/*
 	 * Starting in Gen9, render power gating can leave
 	 * slice/subslice/EU in a partially enabled state. We
-- 
2.17.0

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

  reply	other threads:[~2018-05-29 19:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 19:16 [PATCH v8 0/8] drm/i915: per context slice/subslice powergating Lionel Landwerlin
2018-05-29 19:16 ` Lionel Landwerlin [this message]
2018-05-29 19:16 ` [PATCH v8 2/8] drm/i915: Record the sseu configuration per-context & engine Lionel Landwerlin
2018-05-29 19:16 ` [PATCH v8 3/8] drm/i915/perf: simplify configure all context function Lionel Landwerlin
2018-05-29 19:16 ` [PATCH v8 4/8] drm/i915/perf: reuse intel_lrc ctx regs macro Lionel Landwerlin
2018-05-29 19:16 ` [PATCH v8 5/8] drm/i915/perf: lock powergating configuration to default when active Lionel Landwerlin
2018-05-29 19:16 ` [PATCH v8 6/8] drm/i915: create context image vma in kernel context Lionel Landwerlin
2018-05-29 20:26   ` Michel Thierry
2018-05-29 21:35     ` Lionel Landwerlin
2018-05-29 22:08       ` Chris Wilson
2018-05-30 10:05         ` Lionel Landwerlin
2018-05-30 10:11           ` Chris Wilson
2018-05-29 19:16 ` [PATCH v8 7/8] drm/i915: Expose RPCS (SSEU) configuration to userspace Lionel Landwerlin
2018-05-29 19:16 ` [PATCH v8 8/8] drm/i915: add a sysfs entry to let users set sseu configs Lionel Landwerlin
2018-05-29 19:29 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: per context slice/subslice powergating (rev7) Patchwork
2018-05-29 19:32 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-05-29 19:45 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-29 20:45 ` ✗ 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=20180529191618.19050-2-lionel.g.landwerlin@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --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.