From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tests/kms_frontbuffer_tracking: Fix skips when PSR is not available.
Date: Fri, 1 Feb 2019 10:52:52 +0100 [thread overview]
Message-ID: <b37742cb-c161-3e03-3948-4a8eb22f6d44@linux.intel.com> (raw)
In-Reply-To: <81ed0c63f689aa79f0a0dec6d303044fa9a69d71.camel@intel.com>
Op 31-01-2019 om 21:58 schreef Souza, Jose:
> On Thu, 2019-01-31 at 15:18 +0100, Maarten Lankhorst wrote:
>> Use psr.can_test to determine we can disable PSR, and not skip
>> because
>> PSR is unavailable.
>>
>> Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
>> Cc: José Roberto de Souza <jose.souza@intel.com>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> ---
>> lib/igt_psr.c | 2 +-
>> tests/kms_frontbuffer_tracking.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/igt_psr.c b/lib/igt_psr.c
>> index 5eb6d2c6ace5..6ad2c522f9a4 100644
>> --- a/lib/igt_psr.c
>> +++ b/lib/igt_psr.c
>> @@ -106,7 +106,7 @@ static bool psr_set(int debugfs_fd, int mode)
>>
>> ret = has_psr_debugfs(debugfs_fd);
>> if (ret == -ENODEV) {
>> - igt_skip_on_f(mode >= PSR_MODE_1, "PSR not
>> available\n");
>> + igt_skip("PSR not available\n");
>> return false;
>> }
>>
>> diff --git a/tests/kms_frontbuffer_tracking.c
>> b/tests/kms_frontbuffer_tracking.c
>> index 609f7b41a527..4d15ce1cf1d6 100644
>> --- a/tests/kms_frontbuffer_tracking.c
>> +++ b/tests/kms_frontbuffer_tracking.c
>> @@ -1134,7 +1134,7 @@ static bool disable_features(const struct
>> test_mode *t)
>>
>> fbc_disable();
>> drrs_disable();
>> - return psr_disable(drm.debugfs);
> Although the return true of this functions will cause a unecessary
> igt_display_commit() this changes looks good. In other patch we could
> just drop the return and remove the commit in prepare_subtest_data().
>
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
Thanks, pushed.
This should have been documented, but the function must return true if and only if a modeset is required.
Specifically, It should return false for the debugfs case so we don't do unnecessary modesets,
but true for the modparam case.
I think the rework borked it.
~Maarten
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-01 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 14:18 [igt-dev] [PATCH i-g-t 1/2] lib/psr: Do not use out of bound enum for psr_set Maarten Lankhorst
2019-01-31 14:18 ` [igt-dev] [PATCH i-g-t 2/2] tests/kms_frontbuffer_tracking: Fix skips when PSR is not available Maarten Lankhorst
2019-01-31 20:58 ` Souza, Jose
2019-02-01 9:52 ` Maarten Lankhorst [this message]
2019-01-31 15:12 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/psr: Do not use out of bound enum for psr_set Patchwork
2019-01-31 21:00 ` [igt-dev] [PATCH i-g-t 1/2] " Souza, Jose
2019-01-31 23:59 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] " 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=b37742cb-c161-3e03-3948-4a8eb22f6d44@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jose.souza@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