Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leo <sunpeng.li@amd.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_color: Add 10bpc frame buffer parameterization to subtests
Date: Tue, 17 Dec 2019 09:00:22 -0500	[thread overview]
Message-ID: <1ff03e11-12ab-1355-975a-ffca550ee069@amd.com> (raw)
In-Reply-To: <20191212211326.GU1208@intel.com>



On 2019-12-12 4:13 p.m., Ville Syrjälä wrote:
> On Thu, Dec 12, 2019 at 03:53:34PM -0500, Leo wrote:
>>
>>
>> On 2019-12-12 10:03 a.m., Ville Syrjälä wrote:
>>> On Wed, Dec 11, 2019 at 03:46:36PM -0500, sunpeng.li@amd.com wrote:
>>>> From: Leo Li <sunpeng.li@amd.com>
>>>>
>>>> We'd like to test the hardware pipe's color management with 10bit
>>>> surfaces.
>>>
>>> Why exactly? The pipe color management stuff doesn't care what
>>> pixel format the plane used.
>>>
>>
>> We expose 10bpc support to usermode with color management, so it'd be
>> good to cover it with a test.
>>
>> With amdpgu, color management indeed doesn't care about surface format,
>> since it's all converted to fixed point in hardware beforehand.
> 
> Totally missed this came from AMD folks. Good thing I was still
> correct with my statement then :)
> 
>> But I
>> think it's best to not assume hardware behavior, and test the actual
>> use case instead.
> 
> I think what we would really want is a test that makes sure we can
> achieve the desired precision in the output for some fb depth and
> gamma configuration (sadly the gamma uapi doesn't let us do that
> ATM in a hardware agnostic way). I don't think this test currently
> checks anything like that. But maybe I'm misremebering what it
> actually does.
> 

kms_color does a min and max gamma test where all values are mapped to 0
or 1, so no precision check there... However, it looks like CTM
precision is checked to be within some reasonable threshold, according
to the bpc tested.

I'm not sure if testing LUT precision would make sense as a hw agnostic
test. For AMD hardware at least, the internal representation wasn't designed to
be precise, but to follow human color perception. i.e. precision is lost at
higher color values. So any LUT precision test will have to take vendor-specific
quarks into account. Perhaps this isn't the case for the CTM since the concept
for hw is simpler? At least it works well with i915 and amdgpu FWICT.

Perhaps it's better to have vendor specific tests for LUT precision and
accuracy. I think these tests will at least show that gamma is operational with
10bpc surfaces, which is hw-agnostic enough of a test.

Leo
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-12-17 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 20:46 [igt-dev] [PATCH i-g-t] tests/kms_color: Add 10bpc frame buffer parameterization to subtests sunpeng.li
2019-12-11 20:54 ` Kazlauskas, Nicholas
2019-12-11 21:15 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-12-12  8:12 ` [igt-dev] ✗ GitLab.Pipeline: " Patchwork
2019-12-12 15:03 ` [igt-dev] [PATCH i-g-t] " Ville Syrjälä
2019-12-12 20:53   ` Leo
2019-12-12 21:13     ` Ville Syrjälä
2019-12-17 14:00       ` Leo [this message]
2020-01-02 22:59   ` Harry Wentland
2020-01-02 23:03     ` Harry Wentland
2020-01-08 14:44 ` Leo

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=1ff03e11-12ab-1355-975a-ffca550ee069@amd.com \
    --to=sunpeng.li@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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