public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 2/6] drm/i915: Fix intel_dp_mst_compute_link_config
Date: Tue,  1 Nov 2022 11:42:18 +0200	[thread overview]
Message-ID: <20221101094222.22091-3-stanislav.lisovskiy@intel.com> (raw)
In-Reply-To: <20221101094222.22091-1-stanislav.lisovskiy@intel.com>

We currently always exit that bpp loop because
drm_dp_atomic_find_vcpi_slots doesn't care if we actually
can fit those or not.
I think that wasn't the initial intention here, especially when
we keep trying with lower bpps, we are supposed to keep trying
until we actually find some _working_ configuration, which isn't the
case here.
So added that drm_dp_mst_check here, so that we can make sure
that try all the bpps before we fail.

Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
---
 drivers/gpu/drm/i915/display/intel_dp_mst.c | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
index cd4e61026d98..421bbcaed664 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
@@ -59,6 +59,7 @@ static int intel_dp_mst_compute_link_config(struct intel_encoder *encoder,
 	const struct drm_display_mode *adjusted_mode =
 		&crtc_state->hw.adjusted_mode;
 	int bpp, slots = -EINVAL;
+	int ret = 0;
 
 	mst_state = drm_atomic_get_mst_topology_state(state, &intel_dp->mst_mgr);
 	if (IS_ERR(mst_state))
@@ -84,10 +85,21 @@ static int intel_dp_mst_compute_link_config(struct intel_encoder *encoder,
 						      connector->port, crtc_state->pbn);
 		if (slots == -EDEADLK)
 			return slots;
-		if (slots >= 0)
-			break;
+		if (slots >= 0) {
+			ret = drm_dp_mst_atomic_check(state);
+			/*
+			 * If we got slots >= 0 and we can fit those based on check
+			 * then we can exit the loop. Otherwise keep trying.
+			 */
+			if (!ret)
+				break;
+		}
 	}
 
+	/* Despite slots are non-zero, we still failed the atomic check */
+	if (ret && slots >= 0)
+		slots = ret;
+
 	if (slots < 0) {
 		drm_dbg_kms(&i915->drm, "failed finding vcpi slots:%d\n",
 			    slots);
-- 
2.37.3


  parent reply	other threads:[~2022-11-01  9:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  9:42 [Intel-gfx] [PATCH 0/6] Add DP MST DSC support to i915 Stanislav Lisovskiy
2022-11-01  9:42 ` [Intel-gfx] [PATCH 1/6] drm: Add missing DP DSC extended capability definitions Stanislav Lisovskiy
2022-11-01  9:42 ` Stanislav Lisovskiy [this message]
2022-11-01  9:42 ` [Intel-gfx] [PATCH 3/6] drm/i915: Extract drm_dp_atomic_find_vcpi_slots cycle to separate function Stanislav Lisovskiy
2022-11-01  9:42 ` [Intel-gfx] [PATCH 4/6] drm/i915: Add DSC support to MST path Stanislav Lisovskiy
2022-11-01  9:42 ` [Intel-gfx] [PATCH 5/6] drm/i915: Extract VESA DSC bpp alignment to separate function Stanislav Lisovskiy
2022-11-03 13:21   ` Stanislav Lisovskiy
2022-11-10  0:08     ` Navare, Manasi
2022-11-23 10:05     ` Stanislav Lisovskiy
2022-12-08 18:29       ` Navare, Manasi
2022-11-01  9:42 ` [Intel-gfx] [PATCH 6/6] drm/i915: Bpp/timeslot calculation fixes for DP MST DSC Stanislav Lisovskiy
2022-11-01 13:48   ` kernel test robot
2022-11-03 13:23   ` Stanislav Lisovskiy
2022-11-10 22:23     ` Navare, Manasi
2022-11-22 10:39       ` Lisovskiy, Stanislav
2022-11-22 20:40         ` Navare, Manasi D
2022-11-23 10:07     ` Stanislav Lisovskiy
2022-11-01 12:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add DP MST DSC support to i915 (rev14) Patchwork
2022-11-01 12:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-11-01 12:29 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-11-03 14:46 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for Add DP MST DSC support to i915 (rev16) Patchwork
2022-11-03 15:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-04 10:26 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-11-23 10:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add DP MST DSC support to i915 (rev18) Patchwork
2022-11-23 10:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-11-23 11:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " 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=20221101094222.22091-3-stanislav.lisovskiy@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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