From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 1/8] drm/i915: Extract intel_crtc_ddb_weight()
Date: Fri, 22 Jan 2021 22:56:26 +0200 [thread overview]
Message-ID: <20210122205633.18492-2-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20210122205633.18492-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
skl_ddb_get_pipe_allocation_limits() doesn't care how the weights
for distributing the ddb are caclculated for each pipe. Put that
calculation into a separate function so that such mundane details
are hidden from view.
v2: s/adjusted_mode/pipe_mode/
Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
drivers/gpu/drm/i915/intel_pm.c | 45 ++++++++++++++++++++-------------
1 file changed, 27 insertions(+), 18 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
index 9180db1bfda7..3b5e6836c246 100644
--- a/drivers/gpu/drm/i915/intel_pm.c
+++ b/drivers/gpu/drm/i915/intel_pm.c
@@ -4077,6 +4077,24 @@ u32 skl_ddb_dbuf_slice_mask(struct drm_i915_private *dev_priv,
return slice_mask;
}
+static unsigned int intel_crtc_ddb_weight(const struct intel_crtc_state *crtc_state)
+{
+ const struct drm_display_mode *pipe_mode = &crtc_state->hw.pipe_mode;
+ int hdisplay, vdisplay;
+
+ if (!crtc_state->hw.active)
+ return 0;
+
+ /*
+ * Watermark/ddb requirement highly depends upon width of the
+ * framebuffer, So instead of allocating DDB equally among pipes
+ * distribute DDB based on resolution/width of the display.
+ */
+ drm_mode_get_hv_timing(pipe_mode, &hdisplay, &vdisplay);
+
+ return hdisplay;
+}
+
static u8 skl_compute_dbuf_slices(const struct intel_crtc_state *crtc_state,
u8 active_pipes);
@@ -4091,7 +4109,7 @@ skl_ddb_get_pipe_allocation_limits(struct drm_i915_private *dev_priv,
struct intel_atomic_state *intel_state = to_intel_atomic_state(state);
struct drm_crtc *for_crtc = crtc_state->uapi.crtc;
const struct intel_crtc *crtc;
- u32 pipe_width = 0, total_width_in_range = 0, width_before_pipe_in_range = 0;
+ unsigned int pipe_weight = 0, total_weight = 0, weight_before_pipe = 0;
enum pipe for_pipe = to_intel_crtc(for_crtc)->pipe;
struct intel_dbuf_state *new_dbuf_state =
intel_atomic_get_new_dbuf_state(intel_state);
@@ -4160,18 +4178,11 @@ skl_ddb_get_pipe_allocation_limits(struct drm_i915_private *dev_priv,
*/
ddb_range_size = hweight8(dbuf_slice_mask) * slice_size;
- /*
- * Watermark/ddb requirement highly depends upon width of the
- * framebuffer, So instead of allocating DDB equally among pipes
- * distribute DDB based on resolution/width of the display.
- */
total_slice_mask = dbuf_slice_mask;
for_each_new_intel_crtc_in_state(intel_state, crtc, crtc_state, i) {
- const struct drm_display_mode *pipe_mode =
- &crtc_state->hw.pipe_mode;
enum pipe pipe = crtc->pipe;
- int hdisplay, vdisplay;
- u32 pipe_dbuf_slice_mask;
+ unsigned int weight;
+ u8 pipe_dbuf_slice_mask;
if (!crtc_state->hw.active)
continue;
@@ -4198,14 +4209,13 @@ skl_ddb_get_pipe_allocation_limits(struct drm_i915_private *dev_priv,
if (dbuf_slice_mask != pipe_dbuf_slice_mask)
continue;
- drm_mode_get_hv_timing(pipe_mode, &hdisplay, &vdisplay);
-
- total_width_in_range += hdisplay;
+ weight = intel_crtc_ddb_weight(crtc_state);
+ total_weight += weight;
if (pipe < for_pipe)
- width_before_pipe_in_range += hdisplay;
+ weight_before_pipe += weight;
else if (pipe == for_pipe)
- pipe_width = hdisplay;
+ pipe_weight = weight;
}
/*
@@ -4220,9 +4230,8 @@ skl_ddb_get_pipe_allocation_limits(struct drm_i915_private *dev_priv,
return ret;
}
- start = ddb_range_size * width_before_pipe_in_range / total_width_in_range;
- end = ddb_range_size *
- (width_before_pipe_in_range + pipe_width) / total_width_in_range;
+ start = ddb_range_size * weight_before_pipe / total_weight;
+ end = ddb_range_size * (weight_before_pipe + pipe_weight) / total_weight;
alloc->start = offset + start;
alloc->end = offset + end;
--
2.26.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-01-22 20:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 20:56 [Intel-gfx] [PATCH v3 0/8] drm/i915: Remainder of dbuf state stuff Ville Syrjala
2021-01-22 20:56 ` Ville Syrjala [this message]
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 2/8] drm/i915: Pass the crtc to skl_compute_dbuf_slices() Ville Syrjala
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 3/8] drm/i915: Introduce intel_dbuf_slice_size() Ville Syrjala
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 4/8] drm/i915: Introduce skl_ddb_entry_for_slices() Ville Syrjala
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 5/8] drm/i915: Add pipe ddb entries into the dbuf state Ville Syrjala
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 6/8] drm/i915: Extract intel_crtc_dbuf_weights() Ville Syrjala
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 7/8] drm/i915: Encapsulate dbuf state handling harder Ville Syrjala
2021-01-22 20:56 ` [Intel-gfx] [PATCH v3 8/8] drm/i915: Do a bit more initial readout for dbuf Ville Syrjala
2021-01-23 1:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remainder of dbuf state stuff (rev3) Patchwork
2021-01-23 1:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-23 2:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-23 12:15 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-01-24 22:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remainder of dbuf state stuff (rev4) Patchwork
2021-01-24 22:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-24 23:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-25 0:32 ` [Intel-gfx] ✓ 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=20210122205633.18492-2-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;
as well as URLs for NNTP newsgroup(s).