All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Rob Bradford <robert.bradford@intel.com>
Cc: jesse.barnes@intel.com, intel-gfx@lists.freedesktop.org,
	Dhanya Pillai <dhanya.p.r@intel.com>
Subject: Re: [PATCH] tests/kms_color:Color IGT
Date: Fri, 11 Dec 2015 19:51:04 +0100	[thread overview]
Message-ID: <20151211185104.GU20822@phenom.ffwll.local> (raw)
In-Reply-To: <1449848136.10248.36.camel@intel.com>

On Fri, Dec 11, 2015 at 03:35:36PM +0000, Rob Bradford wrote:
> On Fri, 2015-12-11 at 16:01 +0530, Dhanya Pillai wrote:
> > +	/*Enable red planes and apply unit gamma*/
> > +	fb_color.red = 1;
> > +	fb_color.green =0;
> > +	fb_color.blue = 0;
> > +	unit_gamma = 0; /*0 -> white 1->black*/
> 
> Take the CRC here too, as reference_red and check that crc_white !=
> reference_red. (i.e. check its changed)

Since there's the (fairly minimal) chance that CRCs might collide the igt
library only exports helpers to check for equality, not for inequality. We
do have a basic sanity testcase in BAT which makes sure that CRCs are
somewhat sane and do change as expected though. But in checks it feels a
bit like an unsound validation approach to me, so I just leave out all the
"have things changed" checks.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-11 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 10:31 [PATCH] tests/kms_color:Color IGT Dhanya Pillai
2015-12-11 15:35 ` Rob Bradford
2015-12-11 18:51   ` Daniel Vetter [this message]
2015-12-14  7:43   ` R, Dhanya p
  -- strict thread matches above, loose matches on Subject: below --
2015-11-20 10:27 Dhanya Pillai
2015-11-24 16:36 ` Thomas Wood
2015-11-24 17:08 ` Daniel Vetter
2015-07-13  3:54 Dhanya Pillai
2015-07-13  4:01 ` Sharma, Shashank
2015-07-10 10:32 Dhanya Pillai
2015-07-10 10:41 ` David Weinehall

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=20151211185104.GU20822@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dhanya.p.r@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jesse.barnes@intel.com \
    --cc=robert.bradford@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.