From: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, jeevan.b@intel.com,
kunal1.joshi@intel.com, ramanaidu.naladala@intel.com,
swati2.sharma@intel.com, juha-pekka.heikkila@intel.com,
Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
Subject: [PATCH i-g-t v10 0/1] RFC tests/intel/kms_frontbuffer_tracking: Introduce plane-fbc-dr test
Date: Fri, 21 Feb 2025 00:28:02 +0530 [thread overview]
Message-ID: <20250220185803.1995791-1-santhosh.reddy.guddati@intel.com> (raw)
This feature allows FBC to recompress a subsection of a frame.
When the Dirty Rectangle Enable bit is set in the FBC_DIRTY_CTL register,
and there is a sync flip indication, display will read the scanlines
between (and including) the Dirty Rectangle Start Line and End Line,
in FBC_DIRTY_RECTANGLE, from the uncompressed frame buffer.
Utilise the FP_DAMAGE_CLIPS property in the below subtests to validate
the feature.
1.Implement basic tests for Frame Buffer Compression (FBC) with dirty rectangles.
2.Add tests for dirty rectangles outside the visible region.
3.Include tests for dirtyfb functionality.
4.Support different formats in FBC dirty rectangle tests.
5.Ensure proper CRC validation for each test case.
Santhosh Reddy Guddati (1):
tests/intel/kms_dirty_fbc: Add tests to validate FBC dirty rectangle
feature
tests/intel/kms_fbc_dirty_rect.c | 559 +++++++++++++++++++++++++++++++
tests/meson.build | 1 +
2 files changed, 560 insertions(+)
create mode 100644 tests/intel/kms_fbc_dirty_rect.c
--
2.34.1
next reply other threads:[~2025-02-20 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 18:58 Santhosh Reddy Guddati [this message]
2025-02-20 18:58 ` [PATCH i-g-t v10 1/1] tests/intel/kms_dirty_fbc: Add tests to validate FBC dirty rectangle feature Santhosh Reddy Guddati
2025-02-25 9:14 ` Govindapillai, Vinod
2025-02-20 20:22 ` ✓ Xe.CI.BAT: success for RFC tests/intel/kms_frontbuffer_tracking: Introduce plane-fbc-dr test (rev10) Patchwork
2025-02-20 20:30 ` ✗ i915.CI.BAT: failure " Patchwork
2025-02-21 14:34 ` ✗ Xe.CI.Full: " 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=20250220185803.1995791-1-santhosh.reddy.guddati@intel.com \
--to=santhosh.reddy.guddati@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=juha-pekka.heikkila@intel.com \
--cc=kunal1.joshi@intel.com \
--cc=ramanaidu.naladala@intel.com \
--cc=swati2.sharma@intel.com \
--cc=vinod.govindapillai@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