Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jani.nikula@intel.com, pranay.samala@intel.com,
	karthik.b.s@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH i-g-t 0/8] RFC: Add intel_display module support to module load tests
Date: Wed, 18 Nov 2026 21:14:15 +0530	[thread overview]
Message-ID: <20261118154426.345883-1-jeevan.b@intel.com> (raw)

Kernels split the display code out of i915/xe into a separate
intel_display module. This RFC makes IGT aware of it:

- Fall back to intel_display module parameters when looking up params
  (igt_params, kms_panel_fitting).
- Check for intel_display in the i915/xe module_load load subtests.
- Unload intel_display together with the GPU driver.
- Add an intel_display_module_load test.
- Verify the driver unload result in xe/i915_module_load.

Jeevan B (8):
  lib/igt_params: Fall back to intel_display module parameters
  tests/kms_panel_fitting: Find fastboot param with a dedicated display
    module
  tests/intel/i915_module_load: Check intel_display in load subtest
  tests/intel/xe_module_load: Check intel_display in load subtests
  lib/igt_kmod: Unload intel_display together with the GPU driver
  tests/intel: Add intel_display_module_load test
  tests/intel/xe_module_load: Verify driver unload result
  tests/intel/i915_module_load: Verify driver unload result

 lib/igt_kmod.c                          |  45 +++++
 lib/igt_params.c                        |  48 ++++-
 lib/igt_params.h                        |   1 +
 tests/intel/i915_module_load.c          |  11 +-
 tests/intel/intel_display_module_load.c | 221 ++++++++++++++++++++++++
 tests/intel/xe_module_load.c            |  17 +-
 tests/kms_panel_fitting.c               |  17 +-
 tests/meson.build                       |   1 +
 8 files changed, 341 insertions(+), 20 deletions(-)
 create mode 100644 tests/intel/intel_display_module_load.c

-- 
2.43.0


             reply	other threads:[~2026-11-18 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 15:44 Jeevan B [this message]
2026-11-18 15:44 ` [PATCH i-g-t 1/8] lib/igt_params: Fall back to intel_display module parameters Jeevan B
2026-11-18 15:44 ` [PATCH i-g-t 2/8] tests/kms_panel_fitting: Find fastboot param with a dedicated display module Jeevan B
2026-11-19  9:13   ` Jani Nikula
2026-11-18 15:44 ` [PATCH i-g-t 3/8] tests/intel/i915_module_load: Check intel_display in load subtest Jeevan B
2026-11-18 15:44 ` [PATCH i-g-t 4/8] tests/intel/xe_module_load: Check intel_display in load subtests Jeevan B
2026-11-18 15:44 ` [PATCH i-g-t 5/8] lib/igt_kmod: Unload intel_display together with the GPU driver Jeevan B
2026-11-18 15:44 ` [PATCH i-g-t 6/8] tests/intel: Add intel_display_module_load test Jeevan B
2026-11-18 15:44 ` [PATCH i-g-t 7/8] tests/intel/xe_module_load: Verify driver unload result Jeevan B
2026-11-18 15:44 ` [PATCH i-g-t 8/8] tests/intel/i915_module_load: " Jeevan B
2026-11-19  3:40 ` ✓ Xe.CI.BAT: success for RFC: Add intel_display module support to module load tests Patchwork
2026-11-19 12:46 ` ✗ i915.CI.BAT: failure " Patchwork
2026-11-20  3:40 ` ✗ 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=20261118154426.345883-1-jeevan.b@intel.com \
    --to=jeevan.b@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=karthik.b.s@intel.com \
    --cc=pranay.samala@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