From: Harry Wentland <harry.wentland@amd.com>
To: Swati Sharma <swati2.sharma@intel.com>,
igt-dev@lists.freedesktop.org,
Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
uma.shankar@intel.com
Cc: Sebastian Wick <sebastian.wick@redhat.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
Joshua Ashton <joshua@froggi.es>
Subject: Re: [igt-dev] [PATCH 0/2] Add Colorspace tests to kms_hdr
Date: Mon, 9 Jan 2023 11:25:44 -0500 [thread overview]
Message-ID: <268247cc-bf9c-f80d-baa7-a83147d8036c@amd.com> (raw)
In-Reply-To: <ee85b614-4430-cae3-fb1c-fc94c39a56fb@intel.com>
On 12/30/22 15:06, Swati Sharma wrote:
> Hi Harry,
>
> First of all, why do you think kms_hdr is the right place to add colorspace tests? Can we have amd specific IGT for the same.
> It seems intel doesn't have any plans in near future to expose this debugfs.
> ++Uma ++Bhanu
>
kms_hdr includes the max_bpc tests added by Intel a while back. Colorspace
is similar. Both are mainly required for HDR.
This property and the test is generic in principle but I have not had a
chance to look more closely at the i915 driver to see how it should report
the current colorspace. It should be a straightforward change for an
i915 engineer.
Harry
> On 13-Dec-22 12:54 AM, Harry Wentland wrote:
>> We've had a Colorspace property on the drm_connector
>> but no IGT tests. These patches add IGT tests for this
>> property. They're currently only enabled on amdgpu with
>> the kernel at [1] but could be enabled for other drivers
>> if those drivers decide to expose a debugfs to read the
>> currently applied colorspace.
>>
>> [1] https://gitlab.freedesktop.org/hwentland/linux/-/tree/hdr-colorimetry>>>
>> Cc: Pekka Paalanen <ppaalanen@gmail.com>
>> Cc: Sebastian Wick <sebastian.wick@redhat.com>
>> Cc: Vitaly.Prosyak@amd.com
>> Cc: Uma Shankar <uma.shankar@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Joshua Ashton <joshua@froggi.es>
>> Cc: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
>> Cc: Alex Hung <Alex.Hung@amd.com>
>>
>> Harry Wentland (2):
>> tests/kms_hdr: Add test for output Colorspace
>> tests/kms_hdr: Add suspend and DPMS Colorspace tests
>>
>> lib/igt_kms.c | 51 ++++++++++++++++
>> lib/igt_kms.h | 6 ++
>> tests/kms_hdr.c | 156 ++++++++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 213 insertions(+)
>>
>> --
>> 2.38.1
>>
>
prev parent reply other threads:[~2023-01-09 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 19:24 [igt-dev] [PATCH 0/2] Add Colorspace tests to kms_hdr Harry Wentland
2022-12-12 19:24 ` [igt-dev] [PATCH 1/2] tests/kms_hdr: Add test for output Colorspace Harry Wentland
2022-12-13 11:39 ` Pekka Paalanen
2022-12-13 15:06 ` Harry Wentland
2022-12-12 19:24 ` [igt-dev] [PATCH 2/2] tests/kms_hdr: Add suspend and DPMS Colorspace tests Harry Wentland
2022-12-12 20:28 ` [igt-dev] ✓ Fi.CI.BAT: success for Add Colorspace tests to kms_hdr Patchwork
2022-12-13 13:29 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-12-30 20:06 ` [igt-dev] [PATCH 0/2] " Swati Sharma
2023-01-09 16:25 ` Harry Wentland [this message]
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=268247cc-bf9c-f80d-baa7-a83147d8036c@amd.com \
--to=harry.wentland@amd.com \
--cc=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=joshua@froggi.es \
--cc=ppaalanen@gmail.com \
--cc=sebastian.wick@redhat.com \
--cc=swati2.sharma@intel.com \
--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