From: "Souza, Jose" <jose.souza@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"dhinakaran.pandiyan@gmail.com" <dhinakaran.pandiyan@gmail.com>
Cc: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/psr: Skip if PSR cannot be enabled for the current mode.
Date: Wed, 1 Aug 2018 20:03:23 +0000 [thread overview]
Message-ID: <bf76b70f656afa65fc84a157c27e08a3f5e5a349.camel@intel.com> (raw)
In-Reply-To: <20180801064323.14110-1-dhinakaran.pandiyan@intel.com>
On Tue, 2018-07-31 at 23:43 -0700, Dhinakaran Pandiyan wrote:
> PSR tests on ICL fail waiting for PSR to become active, whereas the
> driver does not enable it on the HW due to unmet timing requirements
> [ 482.485873] [drm:intel_dp_compute_config [i915]] PSR condition
> failed: PSR setup time (330 us) too long
> We should probably bring back the kernel patch that programmed an
> alternate
> mode, but skip tests for now.
>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> ---
> tests/kms_psr.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_psr.c b/tests/kms_psr.c
> index 218b3960..89118ad4 100644
> --- a/tests/kms_psr.c
> +++ b/tests/kms_psr.c
> @@ -193,11 +193,19 @@ static bool sink_support(data_t *data)
> char buf[512];
>
> igt_debugfs_read(data->drm_fd, "i915_edp_psr_status", buf);
> -
> return data->with_psr_disabled ||
> strstr(buf, "Sink_Support: yes\n");
> }
>
> +static bool mode_support(data_t *data)
> +{
> + char buf[512];
> +
> + igt_debugfs_read(data->drm_fd, "i915_edp_psr_status", buf);
> + return data->with_psr_disabled ||
> + strstr(buf, "Enabled: yes\n");
> +}
This could hide bugs in gen <= 9.
> +
> static bool psr_wait_entry_if_enabled(data_t *data)
> {
> if (data->with_psr_disabled)
> @@ -422,6 +430,8 @@ int main(int argc, char *argv[])
> drm_intel_bufmgr_gem_enable_reuse(data.bufmgr);
>
> display_init(&data);
> + igt_require_f(mode_support(&data),
> + "PSR not enabled for current mode\n");
Why not just require that gen is <= 9 or 10(if it is working in CNL)?
and leave a TODO.
> }
>
> igt_subtest("basic") {
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-08-01 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 6:43 [igt-dev] [PATCH i-g-t] tests/psr: Skip if PSR cannot be enabled for the current mode Dhinakaran Pandiyan
2018-08-01 8:47 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-08-01 8:59 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2018-08-01 19:05 ` Dhinakaran Pandiyan
2018-08-01 19:34 ` Chris Wilson
2018-08-01 9:49 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2018-08-01 20:03 ` Souza, Jose [this message]
2018-08-01 21:17 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
2018-08-01 20:19 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-08-01 21:09 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-08-02 4:58 ` [igt-dev] [PATCH i-g-t] " Rodrigo Vivi
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=bf76b70f656afa65fc84a157c27e08a3f5e5a349.camel@intel.com \
--to=jose.souza@intel.com \
--cc=dhinakaran.pandiyan@gmail.com \
--cc=dhinakaran.pandiyan@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;
as well as URLs for NNTP newsgroup(s).