From: Anshuman Gupta <anshuman.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jani.nikula@intel.com, martin.peres@intel.com
Subject: [igt-dev] [PATCH i-g-t v5 1/5] tests/i915_pm_lpsp: Nuke the panel-fitter test
Date: Thu, 9 Apr 2020 11:09:47 +0530 [thread overview]
Message-ID: <20200409053951.26929-2-anshuman.gupta@intel.com> (raw)
In-Reply-To: <20200409053951.26929-1-anshuman.gupta@intel.com>
panel-fitter subtest is only applicable to HASWELL/BROADWELL.
It just tests non-lpsp(lpsp disabled) when panel fitter is
enforced by std 1024x768 mode.
There is no ROI to test non-lpsp kind of thing,
If HSW_GLOBAL power well is not enabled we would see
other display issues in other display tests.
Gen9+ platform has display scaling feature in built per
pipe, as lpsp is all about low power single pipe (PIPE A)
usage, gen9+ platforms also don't require panel-fitter subtest.
This should save some CI cycles.
Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
---
tests/i915/i915_pm_lpsp.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tests/i915/i915_pm_lpsp.c b/tests/i915/i915_pm_lpsp.c
index 42938e10..08f82e7c 100644
--- a/tests/i915/i915_pm_lpsp.c
+++ b/tests/i915/i915_pm_lpsp.c
@@ -219,8 +219,6 @@ igt_main
screens_disabled_subtest(drm_fd, drm_res);
igt_subtest("edp-native")
edp_subtest(drm_fd, drm_res, drm_connectors, devid, false);
- igt_subtest("edp-panel-fitter")
- edp_subtest(drm_fd, drm_res, drm_connectors, devid, true);
igt_subtest("non-edp")
non_edp_subtest(drm_fd, drm_res, drm_connectors);
--
2.26.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-04-09 5:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 5:39 [igt-dev] [PATCH i-g-t v5 0/5] lpsp platform agnostic support Anshuman Gupta
2020-04-09 5:39 ` Anshuman Gupta [this message]
2020-04-09 5:39 ` [igt-dev] [PATCH i-g-t v5 2/5] lib/igt_pm: Add lib func to get lpsp capability Anshuman Gupta
2020-04-14 16:26 ` Manna, Animesh
2020-04-14 16:25 ` Anshuman Gupta
2020-04-15 12:48 ` Anshuman Gupta
2020-04-17 14:08 ` Manna, Animesh
2020-04-09 5:39 ` [igt-dev] [PATCH i-g-t v5 3/5] tests/i915_pm_lpsp: lpsp platform agnostic support Anshuman Gupta
2020-04-17 14:22 ` Manna, Animesh
2020-04-17 15:28 ` Anshuman Gupta
2020-04-17 16:27 ` Manna, Animesh
2020-04-17 16:44 ` Anshuman Gupta
2020-04-20 11:01 ` Manna, Animesh
2020-05-04 5:50 ` Anshuman Gupta
2020-04-09 5:39 ` [igt-dev] [PATCH i-g-t v5 4/5] tests/i915_pm_lpsp: screens-disabled subtest use igt_wait Anshuman Gupta
2020-04-17 14:27 ` Manna, Animesh
2020-04-17 15:30 ` Anshuman Gupta
2020-04-09 5:39 ` [igt-dev] [PATCH i-g-t v5 5/5] tests/i915_pm_rpm: lpsp/non-lpsp screen mode_set_data Anshuman Gupta
2020-04-09 6:41 ` [igt-dev] ✗ Fi.CI.BAT: failure for lpsp platform agnostic support (rev7) Patchwork
2020-04-15 13:54 ` [igt-dev] ✗ GitLab.Pipeline: warning for lpsp platform agnostic support (rev8) Patchwork
2020-04-15 14:02 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-04-16 9:10 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20200409053951.26929-2-anshuman.gupta@intel.com \
--to=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=martin.peres@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