Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
	Shekhar Chauhan <shekhar.chauhan@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: matthew.d.roper@intel.com, clinton.a.taylor@intel.com,
	shekhar.chauhan@intel.com
Subject: Re: [PATCH v5] drm/i915/dp: Increase idle pattern wait timeout to 2ms
Date: Thu, 14 Mar 2024 11:12:03 +0200	[thread overview]
Message-ID: <87wmq5qisc.fsf@intel.com> (raw)
In-Reply-To: <171015867667.7312.2596870350343862692@gjsousa-mobl2>

On Mon, 11 Mar 2024, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Shekhar Chauhan (2024-03-11 01:15:04-03:00)
>>The driver currently waits 1ms for idle patterns,
>>but for Xe2LPD and possibly future display IPs,
>>it requires a 1640us (rounded up to 2ms) timeout
>>whilst waiting for idle patterns for MST streams.
>>
>>To simplify the code, the timeout is uniformly
>>increased by 1ms across all platforms/display IPs.
>>
>>v1: Introduced the 2ms wait timeout.
>>v2: Segregated the wait timeout for platforms before & after LNL.
>>v3: Fixed 2 cosmetic changes.
>>v4: Revert to v2 design with commit message enhancements.
>>v5: Minor cosmetic changes to the commit message.
>>
>>BSpec: 68849
>>Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
>
> Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>

Thanks for the patch and review, pushed to drm-intel-next.

BR,
Jani.

>
>>---
>> drivers/gpu/drm/i915/display/intel_ddi.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>>diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
>>index bea441590204..05ba3642d486 100644
>>--- a/drivers/gpu/drm/i915/display/intel_ddi.c
>>+++ b/drivers/gpu/drm/i915/display/intel_ddi.c
>>@@ -3680,7 +3680,7 @@ static void intel_ddi_set_idle_link_train(struct intel_dp *intel_dp,
>> 
>>         if (intel_de_wait_for_set(dev_priv,
>>                                   dp_tp_status_reg(encoder, crtc_state),
>>-                                  DP_TP_STATUS_IDLE_DONE, 1))
>>+                                  DP_TP_STATUS_IDLE_DONE, 2))
>>                 drm_err(&dev_priv->drm,
>>                         "Timed out waiting for DP idle patterns\n");
>> }
>>-- 
>>2.34.1
>>

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-03-14  9:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  4:15 [PATCH v5] drm/i915/dp: Increase idle pattern wait timeout to 2ms Shekhar Chauhan
2024-03-11 12:04 ` Gustavo Sousa
2024-03-14  9:12   ` Jani Nikula [this message]
2024-03-11 23:39 ` ✗ Fi.CI.BAT: failure for drm/i915/dp: Increase idle pattern wait timeout to 2ms (rev4) Patchwork
2024-03-13  3:54   ` Chauhan, Shekhar
2024-03-13  7:46     ` Illipilli, TejasreeX
2024-03-13  6:45 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-13  8:54 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-14  5:14   ` Chauhan, Shekhar
2024-03-14 18:31     ` Illipilli, TejasreeX
2024-03-14 18:37     ` Illipilli, TejasreeX
2024-03-14 18:33 ` ✓ Fi.CI.IGT: 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=87wmq5qisc.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=clinton.a.taylor@intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=shekhar.chauhan@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