From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 3/3] tests/kms_plane: Throw away yet another bi
Date: Tue, 2 Jul 2019 20:04:50 +0300 [thread overview]
Message-ID: <20190702170450.GV5942@intel.com> (raw)
In-Reply-To: <E7C9878FBA1C6D42A1CA3F62AEB6945F820EE8C5@BGSMSX104.gar.corp.intel.com>
On Tue, Jul 02, 2019 at 04:44:28PM +0000, Shankar, Uma wrote:
>
>
> >-----Original Message-----
> >From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com]
> >Sent: Tuesday, July 2, 2019 7:00 PM
> >To: Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com>
> >Cc: igt-dev@lists.freedesktop.org; Shankar, Uma <uma.shankar@intel.com>
> >Subject: Re: [igt-dev] [PATCH i-g-t 3/3] tests/kms_plane: Throw away yet another bi
> >
> >On Tue, Jul 02, 2019 at 01:20:47PM +0000, Kazlauskas, Nicholas wrote:
> >> On 6/28/19 3:44 PM, Ville Syrjala wrote:
> >> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >> >
> >> > CHV pipe A/C sprites are causing a crc mismatch with BT.601 when we
> >> > keep the six msbs. If we throw away one more bit we get matches for
> >> > BT.601. BT.709 matches even with 6 bits, as do the pipe B planes
> >> > with their programmable CSC. Also IVB and KBL were both happy with 6
> >> > bits, so doesn't seem that that these CHV mismatches are due to bugs
> >> > in our code, just the hw is a bit imprecise.
> >> >
> >> > Cc: Uma Shankar <uma.shankar@intel.com>
> >> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >> With the title of this patch corrected ("Throw away yet another bit"),
> >> this series is:
> >>
> >> Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> >>
> >> These patches are useful to have.
> >>
> >> However, I'm not sure how I feel about the naming on all of these new
> >> *_full functions or if they're really all needed. I think just having
> >> one function that explicitly sets all of this is probably enough
> >> rather than having these 4 new functions.
> >
> >I suppose I could just use igt_create_fb_with_bo_size() and hand roll the solid fill in
> >the test.
>
> Yeah this sounds good. Overall this patch looks ok.
> Reviewed-by: Uma Shankar <uma.shanka@intel.com>
>
> I tested this as well on ICL and looks like below test passes without any failure:
> Subtest pixel-format-pipe-A-planes: SUCCESS (423.398s)
Yeah, it already passes with the current upstream code with the wonky
icsc coefficients. Might be nice to test how many correct bits we can
get with the current vs. fixed coefficents.
> So,
> Tested-by: Uma Shankar <uma.shankar@intel.com>
>
> >--
> >Ville Syrjälä
> >Intel
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-07-02 17:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 19:44 [igt-dev] [PATCH i-g-t 0/3] Test all YCbCr encodings/ranges Ville Syrjala
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 1/3] lib/igt_fb: Allow creating yuv fbs with different encodings/ranges Ville Syrjala
2019-07-02 14:47 ` Shankar, Uma
2019-07-02 17:56 ` [igt-dev] [PATCH i-g-t v2 " Ville Syrjala
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 2/3] tests/kms_plane: Test all YCbCr encodings/ranges Ville Syrjala
2019-07-02 15:09 ` Shankar, Uma
2019-07-02 17:57 ` [igt-dev] [PATCH i-g-t v2 " Ville Syrjala
2019-07-02 18:07 ` Kazlauskas, Nicholas
2019-07-03 17:12 ` Ville Syrjälä
2019-07-03 18:01 ` Kazlauskas, Nicholas
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 3/3] tests/kms_plane: Throw away yet another bi Ville Syrjala
2019-07-02 13:20 ` Kazlauskas, Nicholas
2019-07-02 13:30 ` Ville Syrjälä
2019-07-02 16:44 ` Shankar, Uma
2019-07-02 17:04 ` Ville Syrjälä [this message]
2019-07-03 12:41 ` Shankar, Uma
2019-06-28 22:48 ` [igt-dev] ✓ Fi.CI.BAT: success for Test all YCbCr encodings/ranges Patchwork
2019-06-29 9:45 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-07-02 17:57 ` [igt-dev] ✗ Fi.CI.BAT: failure for Test all YCbCr encodings/ranges (rev2) Patchwork
2019-07-02 18:08 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2019-07-02 18:28 ` [igt-dev] ✓ Fi.CI.BAT: success for Test all YCbCr encodings/ranges (rev3) Patchwork
2019-07-03 16:53 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=20190702170450.GV5942@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=uma.shankar@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