All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@amd.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 v4 0/6] Add writeback changes for intel-supported formats
Date: Thu, 4 Dec 2025 16:07:12 -0700	[thread overview]
Message-ID: <e6c111a3-7700-4b19-abec-bb00052a034b@amd.com> (raw)
In-Reply-To: <20251203094307.3187669-1-sowmiya.s@intel.com>

This series is Reviewed-by: Alex Hung <alex.hung@amd.com>

On 12/3/25 02:43, 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.
> 
> Sowmiya S (6):
>    tests/kms_writeback: Add support for intel-specific formats
>    lib/igt_fb: Validate supported formats for crc calculation
>    tests/kms_writeback: Add intel specific check
>    tests/kms_writeback: Refactor format handling in commit_and_dump_fb
>    tests/kms_writeback: Refactor writeback-fb-id subtest
>    tests/kms_writeback: Refactor writeback-check-output subtest
> 
>   lib/igt_fb.c          |   6 +-
>   tests/kms_writeback.c | 215 +++++++++++++++++++++++-------------------
>   2 files changed, 124 insertions(+), 97 deletions(-)
> 


      parent reply	other threads:[~2025-12-04 23:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03  9:43 [PATCH i-g-t v4 0/6] Add writeback changes for intel-supported formats Sowmiya S
2025-12-03  9:43 ` [PATCH i-g-t v4 1/6] tests/kms_writeback: Add support for intel-specific formats Sowmiya S
2026-01-08  5:14   ` Kandpal, Suraj
2025-12-03  9:43 ` [PATCH i-g-t v4 2/6] lib/igt_fb: Validate supported formats for crc calculation Sowmiya S
2026-01-08  5:16   ` Kandpal, Suraj
2025-12-03  9:43 ` [PATCH i-g-t v4 3/6] tests/kms_writeback: Add intel specific check Sowmiya S
2026-01-08  5:18   ` Kandpal, Suraj
2026-01-08  9:35     ` S, Sowmiya
2025-12-03  9:43 ` [PATCH i-g-t v4 4/6] tests/kms_writeback: Refactor format handling in commit_and_dump_fb Sowmiya S
2026-01-08  5:13   ` Kandpal, Suraj
2026-01-08  9:34     ` S, Sowmiya
2025-12-03  9:43 ` [PATCH i-g-t v4 5/6] tests/kms_writeback: Refactor writeback-fb-id subtest Sowmiya S
2026-01-08  5:25   ` Kandpal, Suraj
2026-01-12  8:56   ` Kamil Konieczny
2026-01-12 15:54     ` S, Sowmiya
2025-12-03  9:43 ` [PATCH i-g-t v4 6/6] tests/kms_writeback: Refactor writeback-check-output subtest Sowmiya S
2026-01-08  5:31   ` Kandpal, Suraj
2025-12-03 10:57 ` ✗ Xe.CI.BAT: failure for Add writeback changes for intel-supported formats (rev4) Patchwork
2025-12-03 10:59 ` ✗ i915.CI.BAT: " Patchwork
2025-12-03 12:36 ` ✓ Xe.CI.Full: success " Patchwork
2025-12-04 23:07 ` Alex Hung [this message]

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=e6c111a3-7700-4b19-abec-bb00052a034b@amd.com \
    --to=alex.hung@amd.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 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.