From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/5] tests/intel/kms_pm_lpsp: Add XE support
Date: Mon, 11 Sep 2023 20:38:31 +0530 [thread overview]
Message-ID: <81bcf6b5-5fe9-0d44-7f14-da035bdd94d1@intel.com> (raw)
In-Reply-To: <75bdc363-2e93-5f1f-90de-4c99d49d85d3@intel.com>
On 11-Sep-23 8:14 PM, Modem, Bhanuprakash wrote:
> Hi Swati,
>
> On Fri-08-09-2023 11:20 pm, Swati Sharma wrote:
>> Add XE driver support for kms pm tests.
>>
>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>> ---
>> tests/intel/kms_pm_lpsp.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/tests/intel/kms_pm_lpsp.c b/tests/intel/kms_pm_lpsp.c
>> index 9b5547cda..7d697b1e2 100644
>> --- a/tests/intel/kms_pm_lpsp.c
>> +++ b/tests/intel/kms_pm_lpsp.c
>> @@ -39,7 +39,7 @@
>> *
>> * SUBTEST: kms-lpsp
>> * Description: This test validates lpsp on all connected outputs on
>> low power PIPE_A
>> - * Driver requirement: i915
>> + * Driver requirement: i915, xe
>> * Functionality: pm_lpsp
>> * Mega feature: Display Power
>> * Run type: FULL
>> @@ -194,8 +194,7 @@ igt_main
>> data_t data = {};
>> igt_fixture {
>> -
>> - data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
>> + data.drm_fd = drm_open_driver_master(DRIVER_INTEL | DRIVER_XE);
>> igt_require(data.drm_fd >= 0);
>> data.debugfs_fd = igt_debugfs_dir(data.drm_fd);
>> igt_require(data.debugfs_fd >= 0);
>> @@ -208,6 +207,7 @@ igt_main
>> igt_describe("This test validates lpsp while all crtc are
>> disabled");
>> igt_subtest("screens-disabled") {
>> + igt_require_i915(data.drm_fd);
>
> Why it is i915 specific?
This test has no ROI if platform supports DC states.
Test requirement not met in function __igt_unique____real_main192, file
../../../usr/src/igt-gpu-tools/tests/intel/kms_pm_lpsp.c:211:
Test requirement: !dmc_supported(data.debugfs_fd)
DC states supported platform don't have ROI for this subtest
Subtest screens-disabled: SKIP (0.000s)
xe+ we have all platforms supporting dc states, so we can skip this test
for xe.
>
> - Bhanu
>
>> igt_require_f(!dmc_supported(data.debugfs_fd),
>> "DC states supported platform don't have ROI for
>> this subtest\n");
>> screens_disabled_subtest(&data);
next prev parent reply other threads:[~2023-09-11 15:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:50 [igt-dev] [PATCH i-g-t 0/5] Add XE support for display PM tests Swati Sharma
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 1/5] tests/intel/kms_pm_backlight: Add XE support Swati Sharma
2023-09-11 14:42 ` Modem, Bhanuprakash
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 2/5] tests/intel/kms_pm_lpsp: " Swati Sharma
2023-09-11 14:44 ` Modem, Bhanuprakash
2023-09-11 15:08 ` Sharma, Swati2 [this message]
2023-09-13 10:42 ` Modem, Bhanuprakash
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 3/5] tests/intel/kms_pm_dc: Use linear modifier to set primary plane Swati Sharma
2023-09-11 14:45 ` Modem, Bhanuprakash
2023-09-11 15:10 ` Sharma, Swati2
2023-09-13 10:43 ` Modem, Bhanuprakash
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 4/5] tests/intel/kms_pm_dc: Use gem_has_lmem() Swati Sharma
2023-09-11 14:51 ` Modem, Bhanuprakash
2023-09-11 15:12 ` Sharma, Swati2
2023-09-08 17:50 ` [igt-dev] [PATCH i-g-t 5/5] tests/intel/kms_pm_dc: Add XE support Swati Sharma
2023-09-11 15:00 ` Modem, Bhanuprakash
2023-09-11 15:13 ` Sharma, Swati2
2023-09-08 19:19 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add XE support for display PM tests Patchwork
2023-09-08 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-09-08 20:25 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-09-09 0:50 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-14 14:03 [igt-dev] [PATCH i-g-t 0/5] " Swati Sharma
2023-09-14 14:03 ` [igt-dev] [PATCH i-g-t 2/5] tests/intel/kms_pm_lpsp: Add XE support Swati Sharma
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=81bcf6b5-5fe9-0d44-7f14-da035bdd94d1@intel.com \
--to=swati2.sharma@intel.com \
--cc=bhanuprakash.modem@intel.com \
--cc=igt-dev@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