From: Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
To: gwan-gyeong.mun@intel.com, igt-dev@lists.freedesktop.org,
jose.souza@intel.com
Subject: [igt-dev] [PATCH i-g-t 0/3] Add FB_DAMAGE_CLIPS prop and new test for Selective fetch
Date: Tue, 8 Dec 2020 22:31:06 +0530 [thread overview]
Message-ID: <20201208170109.23073-1-pankaj.laxminarayan.bharadiya@intel.com> (raw)
Add new test for selective fetch
Pankaj Bharadiya (3):
lib/kms: Add fb damage clip plane property
lib/igt_psr: Add function to check PSR2 selective fetch
tests: Add new PSR2 selective fetch test
lib/igt_kms.c | 3 +
lib/igt_kms.h | 1 +
lib/igt_psr.c | 10 +
lib/igt_psr.h | 1 +
tests/Makefile.sources | 1 +
tests/kms_psr2_sf.c | 649 +++++++++++++++++++++++++++++++++++++++++
tests/meson.build | 1 +
7 files changed, 666 insertions(+)
create mode 100644 tests/kms_psr2_sf.c
--
2.29.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-12-08 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 17:01 Pankaj Bharadiya [this message]
2020-12-08 17:01 ` [igt-dev] [PATCH i-g-t 1/3] lib/kms: Add fb damage clip plane property Pankaj Bharadiya
2020-12-08 17:01 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_psr: Add function to check PSR2 selective fetch Pankaj Bharadiya
2020-12-08 17:01 ` [igt-dev] [PATCH i-g-t 3/3] tests: Add new PSR2 selective fetch test Pankaj Bharadiya
2020-12-16 10:50 ` Mun, Gwan-gyeong
2020-12-21 4:44 ` Laxminarayan Bharadiya, Pankaj
2021-01-04 19:37 ` Mun, Gwan-gyeong
2020-12-08 17:22 ` [igt-dev] [PATCH i-g-t 0/3] Add FB_DAMAGE_CLIPS prop and new test for Selective fetch Souza, Jose
2020-12-08 19:31 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-12-09 0:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-01-08 12:21 ` [igt-dev] [PATCH i-g-t 0/3] " Petri Latvala
-- strict thread matches above, loose matches on Subject: below --
2020-11-18 8:14 Pankaj Bharadiya
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=20201208170109.23073-1-pankaj.laxminarayan.bharadiya@intel.com \
--to=pankaj.laxminarayan.bharadiya@intel.com \
--cc=gwan-gyeong.mun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.