From: Karthik B S <karthik.b.s@intel.com>
To: Sowmiya S <sowmiya.s@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <swati2.sharma@intel.com>, <suraj.kandpal@intel.com>
Subject: Re: [PATCH i-g-t v8 0/9] Add writeback changes for intel-supported formats
Date: Mon, 9 Feb 2026 13:44:32 +0530 [thread overview]
Message-ID: <edac5f23-8a49-4594-adeb-367ace502dbf@intel.com> (raw)
In-Reply-To: <20260204171819.292327-1-sowmiya.s@intel.com>
Hi Sowmiya,
Could you please add a patch in this series to unblocklist kms_writeback
on CI, so that we get the results for this subtest before merging this
series.
Thanks and Regards,
Karthik.B.S
On 2/4/2026 10:48 PM, Sowmiya S wrote:
> This series introduces validation for writeback functionality
> across newly supported formats specific to Intel platforms.
> existing functions with limited format support were retained
> for compatibility. After validating new formats introduced by
> the platform, additional format support was added to the
> writeback test suite. Subtests leveraging common framebuffer
> creation logic were consolidated and dynamic subtest generation
> was implemented to efficiently handle format-specific variations.
> Add negative test cases to validate format and mode.Refactored
> existing test cases to improve efficiency.Add helper function
> to get the default format.
>
> lib/igt_fb.c | 39 +++++++-
> lib/igt_fb.h | 1 +
> tests/kms_writeback.c | 211 +++++++++++++++++++++++++-----------------
> 3 files changed, 162 insertions(+), 89 deletions(-)
>
next prev parent reply other threads:[~2026-02-09 8:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 17:18 [PATCH i-g-t v8 0/9] Add writeback changes for intel-supported formats Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 1/9] tests/kms_writeback: Add support for intel-specific formats Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 2/9] lib/igt_fb: Validate supported formats for crc calculation Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 3/9] tests/kms_writeback: Update checks for zero FB ID and empty writeback commit Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 4/9] lib/igt_fb: Add helper to get bpc from DRM fourcc Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 5/9] tests/kms_writeback: Refactor format handling in commit_and_dump_fb Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 6/9] tests/kms_writeback: Remove unused invalid_fb parameter Sowmiya S
2026-02-05 2:55 ` Kandpal, Suraj
2026-02-04 17:18 ` [PATCH i-g-t v8 7/9] tests/kms_writeback: Refactor writeback-fb-id subtest Sowmiya S
2026-02-04 17:18 ` [PATCH i-g-t v8 8/9] tests/kms_writeback: Refactor writeback-check-output subtest Sowmiya S
2026-02-12 16:04 ` Bilal, Mohammed
2026-02-04 17:18 ` [PATCH i-g-t v8 9/9] tests/kms_writeback: Use helper to fetch default FB format Sowmiya S
2026-02-04 19:07 ` ✓ Xe.CI.BAT: success for Add writeback changes for intel-supported formats (rev8) Patchwork
2026-02-04 19:13 ` ✓ i915.CI.BAT: " Patchwork
2026-02-05 6:13 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-05 9:27 ` ✓ i915.CI.Full: success " Patchwork
2026-02-09 8:14 ` Karthik B S [this message]
2026-02-09 8:34 ` [PATCH i-g-t v8 0/9] Add writeback changes for intel-supported formats Kandpal, Suraj
2026-02-13 7:08 ` Karthik B S
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=edac5f23-8a49-4594-adeb-367ace502dbf@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=sowmiya.s@intel.com \
--cc=suraj.kandpal@intel.com \
--cc=swati2.sharma@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