Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pranay Samala <pranay.samala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, swati2.sharma@intel.com,
	sameer.lattannavar@intel.com, pranay.samala@intel.com
Subject: [PATCH i-g-t v5 0/2] Improve max-bpc query error handling
Date: Thu, 11 Jun 2026 12:12:11 +0530	[thread overview]
Message-ID: <20260611064213.1300403-1-pranay.samala@intel.com> (raw)

This series moves max-bpc failure handling to the helper/API level.

The previous change modified kms_hdr dynamic-subtest flow to handle
max-bpc read failures, but the real issue was that
igt_get_output_max_bpc() handled read/parse failures internally.

Restore the original kms_hdr flow and update
igt_get_output_max_bpc() to return status so callers can explicitly
handle failures with clearer skip/continue decisions and logging.

Pranay Samala (2):
  Revert "tests/kms_hdr: Move capability checks inside dynamic subtests"
  lib/tests: make igt_get_output_max_bpc() return status and handle
    failures in callers

 lib/igt_kms.c                          |  41 ++++--
 lib/igt_kms.h                          |   2 +-
 tests/amdgpu/amd_bypass.c              |   6 +-
 tests/amdgpu/amd_dp_dsc.c              |  10 +-
 tests/intel/kms_dsc.c                  |   5 +-
 tests/intel/kms_frontbuffer_tracking.c |  10 +-
 tests/kms_color_helper.c               |   5 +-
 tests/kms_dither.c                     |   9 +-
 tests/kms_hdr.c                        | 187 +++++++++++++++----------
 9 files changed, 180 insertions(+), 95 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-06-11  6:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  6:42 Pranay Samala [this message]
2026-06-11  6:42 ` [PATCH i-g-t v5 1/2] Revert "tests/kms_hdr: Move capability checks inside dynamic subtests" Pranay Samala
2026-06-17 11:12   ` Sharma, Swati2
2026-06-18  4:53   ` Karthik B S
2026-06-11  6:42 ` [PATCH i-g-t v5 2/2] lib/tests: make igt_get_output_max_bpc() return status and handle failures in callers Pranay Samala
2026-06-17 12:14   ` Kamil Konieczny
2026-06-17 16:25     ` Alex Hung
2026-06-18  3:13     ` Karthik B S
2026-06-11  7:50 ` ✓ Xe.CI.BAT: success for Improve max-bpc query error handling Patchwork
2026-06-11  7:56 ` ✓ i915.CI.BAT: " Patchwork
2026-06-11 15:14 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-12  2:53 ` ✗ i915.CI.Full: " Patchwork
2026-06-15 10:00 ` ✓ i915.CI.Full: success " 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=20260611064213.1300403-1-pranay.samala@intel.com \
    --to=pranay.samala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=karthik.b.s@intel.com \
    --cc=sameer.lattannavar@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