public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2] drm/i915: Don't use the second dbuf slice on icl
Date: Wed, 30 Jan 2019 17:51:10 +0200	[thread overview]
Message-ID: <20190130155110.12918-1-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20190121153143.13604-1-ville.syrjala@linux.intel.com>

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

The code managing the dbuf slices is borked and needs some
real work to fix. In the meantime let's just stop using the
second slice.

v2: Drop the change to intel_enabled_dbuf_slices_num() (Mahesh)

Cc: Mahesh Kumar <mahesh1.sh.kumar@gmail.com>
Reviewed-by: Imre Deak <imre.deak@intel.com> #v1
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 drivers/gpu/drm/i915/intel_pm.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
index 53b706154c94..ed9786241307 100644
--- a/drivers/gpu/drm/i915/intel_pm.c
+++ b/drivers/gpu/drm/i915/intel_pm.c
@@ -3822,8 +3822,13 @@ static u16 intel_get_ddb_size(struct drm_i915_private *dev_priv,
 
 	/*
 	 * 12GB/s is maximum BW supported by single DBuf slice.
+	 *
+	 * FIXME dbuf slice code is broken:
+	 * - must wait for planes to stop using the slice before powering it off
+	 * - plane straddling both slices is illegal in multi-pipe scenarios
+	 * - should validate we stay within the hw bandwidth limits
 	 */
-	if (num_active > 1 || total_data_bw >= GBps(12)) {
+	if (0 && (num_active > 1 || total_data_bw >= GBps(12))) {
 		ddb->enabled_slices = 2;
 	} else {
 		ddb->enabled_slices = 1;
-- 
2.19.2

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

  parent reply	other threads:[~2019-01-30 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 15:31 [PATCH] drm/i915: Don't use the second dbuf slice on icl Ville Syrjala
2019-01-21 16:02 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-01-21 16:25 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-21 21:42 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-22  9:19 ` [PATCH] " Mahesh Kumar
2019-01-25 15:08   ` Imre Deak
2019-01-28  3:41     ` Mahesh Kumar
2019-01-22  9:28 ` Mahesh Kumar
2019-01-25 15:27   ` Ville Syrjälä
2019-01-28  3:54     ` Mahesh Kumar
2019-01-25 15:09 ` Imre Deak
2019-01-30 15:51 ` Ville Syrjala [this message]
2019-01-31  3:48   ` [PATCH v2] " Mahesh Kumar
2019-01-30 17:57 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Don't use the second dbuf slice on icl (rev2) Patchwork
2019-01-30 18:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31  0:24 ` ✓ 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=20190130155110.12918-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox