public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Ap, Kamal" <kamal.ap@intel.com>,
	"Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/psr: Skip PSR tests if sink not reliable
Date: Thu, 24 Oct 2019 23:15:05 +0000	[thread overview]
Message-ID: <c8bc10f4212fb6ee0615d25171fa31c42e75f71b.camel@intel.com> (raw)
In-Reply-To: <20191024150039.GE18842@mdroper-desk1.amr.corp.intel.com>

On Thu, 2019-10-24 at 08:00 -0700, Matt Roper wrote:
> On Wed, Oct 23, 2019 at 02:50:30PM -0700, José Roberto de Souza
> wrote:
> > Right now if sink reported any PSR error or if it fails to
> > acknowledge the PSR wakeup it sets a flag and do not attempt to
> > enable PSR anymore. That is the safest approach to avoid repetitive
> > glitches and allowed us to have PSR enabled by default.
> > 
> > But from time to time even good PSR panels have a PSR error,
> > causing
> > tests to fail. And for now we are not yet to the point were we
> > could
> > try to recover from PSR errors, so lets check for this information
> > in
> > debugfs and skip PSR tests because of sink errors and eliminate
> > this
> > noise from CI runs.
> > 
> > Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Matt Roper <matthew.d.roper@intel.com>
> > Cc: Ap Kamal <kamal.ap@intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109454
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>

Added and pushed

Thanks

> 
> and r-b for the i915 patch as well.
> 
> 
> > ---
> >  lib/igt_psr.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/lib/igt_psr.c b/lib/igt_psr.c
> > index b92ea73f..0e79dcd9 100644
> > --- a/lib/igt_psr.c
> > +++ b/lib/igt_psr.c
> > @@ -33,6 +33,8 @@ static bool psr_active_check(int debugfs_fd, enum
> > psr_mode mode)
> >  	igt_debugfs_simple_read(debugfs_fd, "i915_edp_psr_status", buf,
> >  				sizeof(buf));
> >  
> > +	igt_skip_on(strstr(buf, "PSR sink not reliable: yes"));
> > +
> >  	return strstr(buf, state);
> >  }
> >  
> > -- 
> > 2.23.0
> > 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-10-24 23:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 21:50 [igt-dev] [PATCH i-g-t 1/2] lib/psr: Skip PSR tests if sink not reliable José Roberto de Souza
2019-10-23 21:50 ` [igt-dev] [PATCH i-g-t 2/2] lib/psr: Remove unused function José Roberto de Souza
2019-10-23 22:33 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/psr: Skip PSR tests if sink not reliable Patchwork
2019-10-24 15:00 ` [igt-dev] [PATCH i-g-t 1/2] " Matt Roper
2019-10-24 23:15   ` Souza, Jose [this message]
2019-10-24 18:05 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] " 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=c8bc10f4212fb6ee0615d25171fa31c42e75f71b.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamal.ap@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@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