Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915/display: Increase number of fast wake precharge pulses
Date: Thu, 22 Feb 2024 09:15:15 +0000	[thread overview]
Message-ID: <2a8e2f71a0dfea2d342eeb71f2e32edf4a63129c.camel@intel.com> (raw)
In-Reply-To: <ZdZKycWDtduq6AN0@intel.com>

On Wed, 2024-02-21 at 21:11 +0200, Ville Syrjälä wrote:
> On Wed, Feb 21, 2024 at 09:53:22AM +0200, Jouni Högander wrote:
> > Increasing number of fast wake sync pulses seem to fix problems
> > with
> > certain PSR panels. This should be ok for other panels as well as
> > the eDP
> > specification allows 10...16 precharge pulses and we are still
> > within that
> > range.
> 
> Hmm. Didn't we have some other panel that didn't like the original 16
> precharge pulses? Or maybe that was just because we weren't using the
> formula and thus we had a mismatch wrt. the fast wake stuff?

Original value was 32 for fw pulse len. This was changed to 24
(605f7c731333 drm/i915: Fix fast wake AUX sync len) and back then it
was fixing problem with certain panel model. This didn't match with our
static 42 us io wake time used to calculate io wake line configuration.
Issue with another panel model was fixed by setting it to 18
(b29a20f7c499 drm/i915: Use 18 fast wake AUX sync len) as was expected
by that 42 us io wake time.

> 
> And are we sure this is definitely due to the precharge length
> and not because eg. our idea of the io buffer on latency is too
> short?

In this problematic case io wake / fast wake is ending up to 4 lines.
I.e. io buffer on latency should be increased quite a lot to have any
impact on what is configured as io wake lines in PSR2 CTL. Anyways
based on my testing issue gets fixed by changing the pulse count or
fast wake lines configuration or both. Changing IO wake line
configuration doesn't help.

BR,

Jouni Högander

> 
> > 
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/9739
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_dp_aux.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > b/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > index fad39b2e3022..4641c5bb8fb9 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > @@ -145,7 +145,7 @@ static int intel_dp_aux_sync_len(void)
> >  
> >  static u8 intel_dp_aux_fw_sync_len(void)
> >  {
> > -       u8 precharge = 10; /* 10-16 */
> > +       u8 precharge = 12; /* 10-16 */
> 
> I think we need a comment to remind people why we are using a
> specific
> value.
> 
> >         u8 preamble = 8;
> >  
> >         return precharge + preamble;
> > -- 
> > 2.34.1
> 


  reply	other threads:[~2024-02-22  9:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  7:53 [PATCH 0/3] IO and fast wake lines calculation and increase fw sync length Jouni Högander
2024-02-21  7:53 ` [PATCH 1/3] drm/i915/display: Add aux function pointer for fast wake sync pulse count Jouni Högander
2024-02-21 19:05   ` Ville Syrjälä
2024-02-21  7:53 ` [PATCH 2/3] drm/i915/psr: Improve fast and IO wake lines calculation Jouni Högander
2024-02-21 19:05   ` Ville Syrjälä
2024-02-21 19:16     ` Ville Syrjälä
2024-02-21 21:45       ` Ville Syrjälä
2024-02-22  9:28         ` Hogander, Jouni
2024-02-22  8:39     ` Hogander, Jouni
2024-02-22  0:42   ` kernel test robot
2024-02-26 10:05   ` Dan Carpenter
2024-02-21  7:53 ` [PATCH 3/3] drm/i915/display: Increase number of fast wake precharge pulses Jouni Högander
2024-02-21 19:11   ` Ville Syrjälä
2024-02-22  9:15     ` Hogander, Jouni [this message]
2024-02-21 10:18 ` ✗ Fi.CI.CHECKPATCH: warning for IO and fast wake lines calculation and increase fw sync length Patchwork
2024-02-21 10:18 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-02-21 10:32 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-21 12:20 ` ✗ 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=2a8e2f71a0dfea2d342eeb71f2e32edf4a63129c.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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