All of 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>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v5 5/5] drm/i915/display: Increase number of fast wake precharge pulses
Date: Wed, 13 Mar 2024 06:20:34 +0000	[thread overview]
Message-ID: <535728881bacc3f5aaa5c37e91c443d79ebe2a9d.camel@intel.com> (raw)
In-Reply-To: <ZfCGekSEs_gS9zUZ@intel.com>

On Tue, 2024-03-12 at 18:44 +0200, Ville Syrjälä wrote:
> On Fri, Mar 08, 2024 at 01:00:39PM +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.
> > 
> > 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 7e69be100d90..5dff1bc85d61 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)
> >  
> >  int intel_dp_aux_fw_sync_len(void)
> >  {
> > -       int precharge = 10; /* 10-16 */
> > +       int precharge = 12; /* 10-16 */
> 
> This is still giving me allergies because Windows doesn't have
> anything like this. So the mystery is how does Windows work?
> This was an actual production machine I take it?

Not sure if it's already on market. To my understanding it's production
machine.

The problematic panel here is successfully used on older platform (RPL)
but now we are seeing glitches when used on MTL. More discussion about
the issue : https://gitlab.freedesktop.org/drm/intel/-/issues/9739

> 
> Did we have look at the error bits in PSR2_DEBUG to see if there
> is some difference between the working and non-working values?

There is no error bits in PSR2_DEBUG. Just bit 13 indicating "FastWake
Done"
> 
> Anyways, this at least needs a proper comment to explain why
> we're not usign the standard value.

Ok, I will add that comment and send a new version.

BR,

Jouni Högander

> 
> >         int preamble = 8;
> >  
> >         return precharge + preamble;
> > -- 
> > 2.34.1
> 


  reply	other threads:[~2024-03-13  6:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 11:00 [PATCH v5 0/5] IO and fast wake lines calculation and increase fw sync length Jouni Högander
2024-03-08 11:00 ` [PATCH v5 1/5] drm/i915/display: Make intel_dp_aux_fw_sync_len available for PSR code Jouni Högander
2024-03-08 14:37   ` Ville Syrjälä
2024-03-08 11:00 ` [PATCH v5 2/5] drm/i915/psr: Improve fast and IO wake lines calculation Jouni Högander
2024-03-08 14:37   ` Ville Syrjälä
2024-03-08 11:00 ` [PATCH v5 3/5] drm/i915/psr: Calculate IO wake and fast wake lines for DISPLAY_VER < 12 Jouni Högander
2024-03-08 14:38   ` Ville Syrjälä
2024-03-08 11:00 ` [PATCH v5 4/5] drm/i915/psr: Add IO buffer wake times for LunarLake and beyond Jouni Högander
2024-03-08 14:39   ` Ville Syrjälä
2024-03-08 14:56     ` Ville Syrjälä
2024-03-12 11:30       ` Hogander, Jouni
2024-03-08 11:00 ` [PATCH v5 5/5] drm/i915/display: Increase number of fast wake precharge pulses Jouni Högander
2024-03-12 16:44   ` Ville Syrjälä
2024-03-13  6:20     ` Hogander, Jouni [this message]
2024-03-08 14:10 ` ✗ Fi.CI.SPARSE: warning for IO and fast wake lines calculation and increase fw sync length (rev5) Patchwork
2024-03-08 14:29 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-09  4:17 ` ✓ 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=535728881bacc3f5aaa5c37e91c443d79ebe2a9d.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.