Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kahola <mika.kahola@intel.com>
To: Ander Conselvan de Oliveira
	<ander.conselvan.de.oliveira@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v3] lib/igt_kms: Force outputs to use full range RGB
Date: Tue, 09 May 2017 13:22:51 +0300	[thread overview]
Message-ID: <1494325371.6603.57.camel@intel.com> (raw)
In-Reply-To: <20170418130402.15485-1-ander.conselvan.de.oliveira@intel.com>

On Tue, 2017-04-18 at 16:04 +0300, Ander Conselvan de Oliveira wrote:
> In at least SKL and GLK (possibly other devices too), using a cursor
> plane to scan out an fb might result in a different pipe crc than
> when
> using a regular plane at the same position with the same fb while
> using
> the CSC logic to limit the color range. The differences could be
> caused
> by the cursor plane being limited to 8 bpc while the regular planes
> support higher bit depths, leading to slightly different values to be
> used internally. This is evidenced by the failures happening with
> specific color values, 0.5 for example, but that's mostly
> speculation.
> 
> To avoid misterious failures caused by limited range rgb, force all
> tests to use full range. It is still possible for tests to override
> this
> if necessary.
By this way, we know for sure what is the color range in use.

Reviewed-by: Mika Kahola <mika.kahola@intel.com>

> 
> v2: Add more details to the commit message.
> v3: Force all tests to use full range.
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Ander Conselvan de Oliveira
> <ander.conselvan.de.oliveira@intel.com>
> ---
>  lib/igt_kms.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index 5811414..9f72913 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -1455,10 +1455,15 @@ static void igt_output_refresh(igt_output_t
> *output)
>  			       -1);
>  	}
>  
> -	if (output->config.connector)
> +	if (output->config.connector) {
>  		igt_atomic_fill_connector_props(display, output,
>  			IGT_NUM_CONNECTOR_PROPS,
> igt_connector_prop_names);
>  
> +		kmstest_set_connector_broadcast_rgb(display->drm_fd,
> +						    output-
> >config.connector,
> +						    BROADCAST_RGB_FU
> LL);
> +	}
> +
>  	if (output->use_override_mode)
>  		output->config.default_mode = output->override_mode;
>  
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-05-09 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  7:40 [PATCH i-g-t 1/2] kms_cursor_crc: Force the test to run in full RGB range Ander Conselvan de Oliveira
2017-04-06  7:40 ` [PATCH i-g-t 2/2] kms_cursor_limited: Test crc matches between cursor and overlay planes Ander Conselvan de Oliveira
2017-04-11 11:13 ` [PATCH i-g-t v2] kms_cursor_crc: Force the test to run in full RGB range Ander Conselvan de Oliveira
2017-04-18 13:04   ` [PATCH i-g-t v3] lib/igt_kms: Force outputs to use full range RGB Ander Conselvan de Oliveira
2017-05-09 10:22     ` Mika Kahola [this message]
2017-05-10  6:37       ` Conselvan De Oliveira, Ander

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=1494325371.6603.57.camel@intel.com \
    --to=mika.kahola@intel.com \
    --cc=ander.conselvan.de.oliveira@intel.com \
    --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