public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] tests/kms_psr_sink_crc: Create test to test PSR by checking panel CRC.
Date: Fri, 17 Jan 2014 12:50:03 +0200	[thread overview]
Message-ID: <20140117105003.GQ9454@intel.com> (raw)
In-Reply-To: <20140116164750.GC4770@phenom.ffwll.local>

On Thu, Jan 16, 2014 at 05:47:50PM +0100, Daniel Vetter wrote:
> On Wed, Jan 15, 2014 at 04:57:28PM -0200, Rodrigo Vivi wrote:
> > Hi Ville and Daniel,
> > 
> > Ville, since this is heavily based on your kms_fbc_psr I'd appreciate
> > your comments here please.
> > Mainly regarding the page_flip+mmaps which I'm not sure how usefull
> > they are on this psr case.
> > Or my implementation is so wrong that they aren't being useful at all.
> > 
> > Daniel, is this test what you had in mind? All comments, bikesheds,
> > blames are appreciated! ;)
> 
> Maybe I miss it, but Ville's fbc testcase not only checks that the crc
> change, but that the new one perfectly matches the new frame. This is
> useful for catching partial updates ...

That's actually only true for the PAGE_FLIP test. The others (including
the PAGE_FLIP_AND variants) just check that the crc doesn't match. But
I suppose it should be possible to extend that to all the cases if we
want to.

As far as this PSR test case goes, the PAGE_FLIP_AND variant handling is
pretty much busted. The only case where you actually do the page flip
is TEST_PAGE_FLIP_AND_MMAP_GTT, and even then since the reference crc
matches the original frame, the page flip itself would already cause the
test to pass, so it's not actually testing the GTT write at all.

The rest looks pretty much OK. It's mostly a copy of kms_fbc_crc though,
so I wonder if we should try to unify them, just add some flag to
indicate if we should be doing PSR or FBC tests.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-01-17 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 18:52 [PATCH] tests/kms_psr_sink_crc: Create test to test PSR by checking panel CRC Rodrigo Vivi
2014-01-15 18:57 ` Rodrigo Vivi
2014-01-16 16:47   ` Daniel Vetter
2014-01-17 10:50     ` Ville Syrjälä [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-23 18:18 [PATCH 2/3] " Rodrigo Vivi
2014-01-28 19:48 ` [PATCH] " Rodrigo Vivi
2014-01-29 14:56   ` Rodrigo Vivi
2014-01-29 19:25     ` Daniel Vetter
2014-02-05 19:05       ` Rodrigo Vivi

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=20140117105003.GQ9454@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /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