From: Daniel Vetter <daniel@ffwll.ch>
To: Uma Shankar <uma.shankar@intel.com>
Cc: igt-dev@lists.freedesktop.org, ville.syrjala@intel.com,
maarten.lankhorst@intel.com
Subject: Re: [igt-dev] [v4] tests/kms_color: Fix CRC mismatch issues with ctm test
Date: Fri, 29 Mar 2019 10:05:14 +0100 [thread overview]
Message-ID: <20190329090514.GH2665@phenom.ffwll.local> (raw)
In-Reply-To: <20190329090059.GG2665@phenom.ffwll.local>
On Fri, Mar 29, 2019 at 10:00:59AM +0100, Daniel Vetter wrote:
> On Fri, Mar 29, 2019 at 02:49:15AM +0530, Uma Shankar wrote:
> > Due to Gamma/Degamma limitation with precision (lack of
> > exact 1.0 representation) due to ABI restriction, applying
>
> Huh, why? That sounds like a conversion bug in our gamma table handler.
> 0xffff == 1.0 if we don't treat it like that that's a driver bug. The
> gamma table is _not_ fixed point, but linear range from 0-0xffff. Which is
> unlike the ctm (which due to an uapi accident has a really hilarious fixed
> point with sign bit format).
>
> Please don't paper over driver bugs :-)
Can you pls also review existing gamma igt coverage to make sure we're
catching this? Or maybe it's just the testcase that fills the gamma table
the wrong way.
I also noticed that the documentation is kinda wrong in the kernel, since
it talks about 0.16 fixed point. 0.ffff = 1.0 definitely needs to hold by
convention at least, and ideally we'd round this stuff correctly for
intermediate values too. But as long as we have fewer than 16bits of gamma
precision it will only matter for 1.0/0xffff.
-Daniel
> -Daniel
>
> > linear gamma affects crc. This patch fixes the same by making
> > ctm tests independant of gamma/degamma.
> >
> > v2: Disable degamma/gamma programming for ctm max test as it
> > leads to crc mimsmatch. Limiting it to this test case alone as
> > other tests need it to be enabled, hence not touching those
> > scenarios.
> >
> > v3: Fixed a fumble with compilation.
> >
> > v4: Disabling degamma and gamma for ctm max tests, after the logic
> > in kernel has been updated by Ville's series.
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108147
> > Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> > ---
> > tests/kms_color.c | 15 +++++++++++++--
> > 1 file changed, 13 insertions(+), 2 deletions(-)
> >
> > diff --git a/tests/kms_color.c b/tests/kms_color.c
> > index decf3c2..0951ffc 100644
> > --- a/tests/kms_color.c
> > +++ b/tests/kms_color.c
> > @@ -696,8 +696,19 @@ static bool test_pipe_ctm(data_t *data,
> > igt_assert(fb_modeset_id);
> > igt_plane_set_fb(primary, &fb_modeset);
> >
> > - set_degamma(data, primary->pipe, degamma_linear);
> > - set_gamma(data, primary->pipe, gamma_linear);
> > + /*
> > + * Don't program LUT's for max CTM cases as limitation of
> > + * representing 1.0 due to ABI limits causes crc mismatch
> > + */
> > + if (memcmp(before, after, sizeof(color_t))) {
> > + set_degamma(data, primary->pipe, degamma_linear);
> > + set_gamma(data, primary->pipe, gamma_linear);
> > + } else {
> > + /* Disable Degamma and Gamma for ctm max test */
> > + disable_degamma(primary->pipe);
> > + disable_gamma(primary->pipe);
> > + }
> > +
> > disable_ctm(primary->pipe);
> > igt_display_commit(&data->display);
> >
> > --
> > 1.9.1
> >
> > _______________________________________________
> > igt-dev mailing list
> > igt-dev@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/igt-dev
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-29 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 21:19 [igt-dev] [v4] tests/kms_color: Fix CRC mismatch issues with ctm test Uma Shankar
2019-03-28 20:56 ` Ville Syrjälä
2019-03-28 21:31 ` Shankar, Uma
2019-03-28 21:41 ` Shankar, Uma
2019-03-28 21:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Fix CRC mismatch issues with ctm test (rev7) Patchwork
2019-03-29 7:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-29 9:00 ` [igt-dev] [v4] tests/kms_color: Fix CRC mismatch issues with ctm test Daniel Vetter
2019-03-29 9:05 ` Daniel Vetter [this message]
2019-03-29 10:38 ` Ville Syrjälä
2019-04-01 7:26 ` Daniel Vetter
2019-04-01 17:51 ` Ville Syrjälä
2019-04-02 8:52 ` Daniel Vetter
2019-04-02 12:54 ` Shankar, Uma
2019-04-03 8:32 ` Daniel Vetter
2019-04-03 9:29 ` Shankar, Uma
-- strict thread matches above, loose matches on Subject: below --
2019-03-28 21:59 Uma Shankar
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=20190329090514.GH2665@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=igt-dev@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@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