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 0/2] Refactor DRM Debug Severity Handling for enhanced precision
Date: Mon, 10 Mar 2025 22:45:37 +0530 [thread overview]
Message-ID: <20250310171539.273699-1-pranay.samala@intel.com> (raw)
This commit refactors the DRM debug severity logic to provide more
precise control over the debug output by using bitwise operations.
The previous approach lacked flexibility, as it set the debug log
directly, but this change ensures that only specific bits in the
DRM debug mask are modified.
By unsetting unwanted bits and allowing the function to set only the
passed bits, we gain more granular control over the logging output.
Pranay Samala (2):
lib/igt_sysfs: Update DRM debug severity handling to use bitmask for
verbosity control
tests/kms: Simplify DRM debug severity update
lib/igt_sysfs.c | 54 +++++++++++++------------
lib/igt_sysfs.h | 19 +++++++--
tests/intel/kms_dp_linktrain_fallback.c | 12 ++----
tests/kms_atomic_transition.c | 11 +----
tests/kms_cursor_legacy.c | 10 +----
5 files changed, 50 insertions(+), 56 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-10 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 17:15 Pranay Samala [this message]
2025-03-10 17:15 ` [PATCH i-g-t 1/2] lib/igt_sysfs: Update DRM debug severity handling to use bitmask for verbosity control Pranay Samala
2025-03-11 8:49 ` Jani Nikula
2025-03-10 17:15 ` [PATCH i-g-t 2/2] tests/kms: Simplify DRM debug severity update Pranay Samala
2025-03-11 8:55 ` Jani Nikula
2025-03-11 0:47 ` ✓ Xe.CI.BAT: success for Refactor DRM Debug Severity Handling for enhanced precision Patchwork
2025-03-11 1:05 ` ✓ i915.CI.BAT: " Patchwork
2025-03-11 20:44 ` ✗ Xe.CI.Full: failure " 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=20250310171539.273699-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