From: Pranay Samala <pranay.samala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, kunal1.joshi@intel.com,
sameer.lattannavar@intel.com, pranay.samala@intel.com
Subject: [PATCH i-g-t v2 0/2] Refactor DRM Debug Severity Handling for enhanced precision
Date: Thu, 20 Mar 2025 14:37:53 +0530 [thread overview]
Message-ID: <20250320090755.482723-1-pranay.samala@intel.com> (raw)
This patch addresses the need for more flexible handling of the debug
mask in the test framework. The changes enable users to pass a bitmask
option during execution, allowing for dynamic updates to the debug
mask as required. If no mask is provided, the debug mask defaults to 0x4.
Additionally, the exit handler has been updated to restore the original
debug mask at the end of the test, ensuring consistency. This
modification improves the flexibility and robustness of the DRM debug
logic, making it easier to control the debug mask throughout the test.
Pranay Samala (2):
lib/igt_sysfs: Update DRM debug mask handling for verbosity control
tests/kms: Simplify DRM debug mask update
lib/igt_sysfs.c | 61 ++++++++++++++-----------
lib/igt_sysfs.h | 20 ++++++--
tests/intel/kms_dp_linktrain_fallback.c | 40 ++++++++++++----
tests/kms_atomic_transition.c | 25 +++++-----
tests/kms_cursor_legacy.c | 38 +++++++++++----
5 files changed, 123 insertions(+), 61 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-20 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 9:07 Pranay Samala [this message]
2025-03-20 9:07 ` [PATCH i-g-t v2 1/2] lib/igt_sysfs: Update DRM debug mask handling for verbosity control Pranay Samala
2025-03-21 11:13 ` Jani Nikula
2025-03-20 9:07 ` [PATCH i-g-t v2 2/2] tests/kms: Simplify DRM debug mask update Pranay Samala
2025-03-20 9:32 ` ✓ Xe.CI.BAT: success for Refactor DRM Debug Severity Handling for enhanced precision (rev2) Patchwork
2025-03-20 9:52 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-20 10:23 ` ✗ 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=20250320090755.482723-1-pranay.samala@intel.com \
--to=pranay.samala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=kunal1.joshi@intel.com \
--cc=sameer.lattannavar@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