From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] tests/kms_psr_sink_crc: Create test to test PSR by checking panel CRC.
Date: Wed, 29 Jan 2014 20:25:38 +0100 [thread overview]
Message-ID: <20140129192538.GL7444@phenom.ffwll.local> (raw)
In-Reply-To: <1391007386-8822-1-git-send-email-rodrigo.vivi@gmail.com>
On Wed, Jan 29, 2014 at 12:56:26PM -0200, Rodrigo Vivi wrote:
> v2: Wait psr enable with timeout and more subtest added.
> v3: Add wait for v_blank leeting test more reliable and preparing to
> add Baytrail per-pipe tests.
> v4: Call busy_ioctl on mmap_gtt to match the real usage and remove the need
> of inactivate on set_domain, what was semantically wrong.
Like I've said in the other thread, iirc v3 is the right test. At least
it's the same logic as we have in the fbc test, so if we change this we
need to do some funny history digging and adjust it in both places.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-01-29 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 18:18 [PATCH 1/3] tests/kms_sink_crc_basic: Basic test to verify Sink CRC debugfs Rodrigo Vivi
2014-01-23 18:18 ` [PATCH 2/3] tests/kms_psr_sink_crc: Create test to test PSR by checking panel CRC Rodrigo Vivi
2014-01-28 19:48 ` [PATCH] " Rodrigo Vivi
2014-01-29 14:56 ` Rodrigo Vivi
2014-01-29 19:25 ` Daniel Vetter [this message]
2014-02-05 19:05 ` Rodrigo Vivi
2014-01-23 18:18 ` [PATCH 3/3] test/pm_psr: Add Baytrail simple pm_psr test Rodrigo Vivi
-- strict thread matches above, loose matches on Subject: below --
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ä
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=20140129192538.GL7444@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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