From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Jeevan B <jeevan.b@intel.com>
Subject: [igt-dev] [PATCH i-g-t 0/2] Add a new IGT test to validate DC3CO state.
Date: Tue, 1 Oct 2019 17:02:55 +0530 [thread overview]
Message-ID: <1569929577-13291-1-git-send-email-jeevan.b@intel.com> (raw)
This test is creating a vpb scenario for
selective frame update and validating
that DC state stays in DC3CO during execution.
Anshuman Gupta (1):
igt/i915/i915_pm_dc: DC3CO PSR2 helpers
Jeevan B (1):
Add a new IGT test to validate DC3CO state
lib/igt_psr.c | 11 +++
lib/igt_psr.h | 1 +
tests/i915/i915_pm_dc.c | 180 ++++++++++++++++++++++++++++++++++++++++++++++--
3 files changed, 186 insertions(+), 6 deletions(-)
--
2.7.4
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-10-01 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 11:32 Jeevan B [this message]
2019-10-01 11:32 ` [igt-dev] [PATCH i-g-t 1/2] igt/i915/i915_pm_dc: DC3CO PSR2 helpers Jeevan B
2019-10-01 11:32 ` [igt-dev] [PATCH i-g-t 2/2] Add a new IGT test to validate DC3CO state Jeevan B
2019-10-02 16:10 ` [igt-dev] [PATCH i-g-t 2/2] Add a new IGT test to validate DC3CO statey Anshuman Gupta
2019-10-01 12:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Add a new IGT test to validate DC3CO state. (rev3) Patchwork
2019-10-01 17:58 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-10-02 9:32 ` Anshuman Gupta
[not found] <1572355751-24313-1-git-send-email-jeevan.b@intel.com>
2019-10-30 12:57 ` [igt-dev] [PATCH i-g-t 0/2] Add a new IGT test to validate DC3CO state Arkadiusz Hiler
-- strict thread matches above, loose matches on Subject: below --
2019-10-17 10:34 Jeevan B
2019-09-25 12:12 Jeevan B
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=1569929577-13291-1-git-send-email-jeevan.b@intel.com \
--to=jeevan.b@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