From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>,
marcin.bernatowicz@intel.com, kamil.konieczny@linux.intel.com,
katarzyna.piecielska@intel.com, zbigniew.kempczynski@intel.com,
ewelina.musial@intel.com
Subject: [PATCH v2 i-g-t 0/6] Replace intel_sysfs_debugfs
Date: Fri, 13 Jun 2025 12:51:39 +0200 [thread overview]
Message-ID: <20250613105146.106581-1-peter.senna@linux.intel.com> (raw)
This series:
- moves shared function to lib/igt_dir
- creates gpu agnostic tests
- core_debugfs
- core_debugfs_display_on_off
- core_sysfs
- creates the xe-specific test
- xe_debugfs (complementary to core_debugfs*)
- Updates testlists and scripts
- deletes tests/intel_sysfs_debugfs
Cc: marcin.bernatowicz@intel.com
Cc: kamil.konieczny@linux.intel.com
Cc: katarzyna.piecielska@intel.com
Cc: zbigniew.kempczynski@intel.com
Cc: ewelina.musial@intel.com
Peter Senna Tschudin (6):
lib/igt_dir: Directory processing and flexible file handling
tests: Add core_debugfs
tests: Add core_debugfs_display_on_off
tests: Add core_sysfs
tests: Add xe_debugfs
tests/intel: Remove intel_sysfs_debugfs
docs/code_coverage.md | 18 +-
lib/igt_dir.c | 260 ++++++++++++++
lib/igt_dir.h | 61 ++++
lib/meson.build | 1 +
scripts/code_cov_selftest.sh | 2 +-
tests/core_debugfs.c | 54 +++
tests/core_debugfs_display_on_off.c | 171 +++++++++
tests/core_sysfs.c | 58 +++
tests/intel-ci/fast-feedback.testlist | 4 +-
tests/intel-ci/xe-fast-feedback.testlist | 8 +-
tests/intel/intel_sysfs_debugfs.c | 430 -----------------------
tests/intel/xe_debugfs.c | 208 +++++++++++
tests/intel/xe_test_config.json | 2 +-
tests/meson.build | 5 +-
14 files changed, 834 insertions(+), 448 deletions(-)
create mode 100644 lib/igt_dir.c
create mode 100644 lib/igt_dir.h
create mode 100644 tests/core_debugfs.c
create mode 100644 tests/core_debugfs_display_on_off.c
create mode 100644 tests/core_sysfs.c
delete mode 100644 tests/intel/intel_sysfs_debugfs.c
create mode 100644 tests/intel/xe_debugfs.c
--
2.43.0
next reply other threads:[~2025-06-13 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 10:51 Peter Senna Tschudin [this message]
2025-06-13 10:51 ` [PATCH v2 i-g-t 1/6] lib/igt_dir: Directory processing and file handling Peter Senna Tschudin
2025-06-13 10:51 ` [PATCH v2 i-g-t 2/6] tests: Add core_debugfs Peter Senna Tschudin
2025-06-13 13:49 ` Michal Wajdeczko
2025-06-13 10:51 ` [PATCH v2 i-g-t 3/6] tests: Add core_debugfs_display_on_off Peter Senna Tschudin
2025-06-13 17:54 ` Kamil Konieczny
2025-06-24 5:21 ` Karthik B S
2025-06-13 10:51 ` [PATCH v2 i-g-t 4/6] tests: Add core_sysfs Peter Senna Tschudin
2025-06-13 10:51 ` [PATCH v2 i-g-t 5/6] tests: Add xe_debugfs Peter Senna Tschudin
2025-06-13 10:51 ` [PATCH v2 i-g-t 6/6] tests/intel: Remove intel_sysfs_debugfs Peter Senna Tschudin
2025-06-13 13:04 ` ✓ Xe.CI.BAT: success for Replace intel_sysfs_debugfs (rev3) Patchwork
2025-06-13 13:10 ` ✓ i915.CI.BAT: " Patchwork
2025-06-13 14:59 ` ✗ i915.CI.Full: failure " Patchwork
2025-06-15 0:04 ` ✗ 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=20250613105146.106581-1-peter.senna@linux.intel.com \
--to=peter.senna@linux.intel.com \
--cc=ewelina.musial@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=marcin.bernatowicz@intel.com \
--cc=zbigniew.kempczynski@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