From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com,
"Juha-Pekka Heikkilä" <juha-pekka.heikkila@intel.com>
Subject: [Intel-gfx] [PATCH 0/3] drm/i915: from module params to device params
Date: Tue, 7 Apr 2020 12:49:35 +0300 [thread overview]
Message-ID: <cover.1586252867.git.jani.nikula@intel.com> (raw)
This is still pending igt changes to switch from module param sysfs to the
device param debugfs. Posting for early review.
BR,
Jani.
Cc: Juha-Pekka Heikkilä <juha-pekka.heikkila@intel.com>
Cc: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
Jani Nikula (3):
drm/i915/params: don't expose inject_probe_failure in debugfs
drm/i915/params: prevent changing module params runtime
drm/i915/params: switch to device specific parameters
drivers/gpu/drm/i915/display/intel_bios.c | 6 +--
drivers/gpu/drm/i915/display/intel_crt.c | 4 +-
drivers/gpu/drm/i915/display/intel_csr.c | 6 +--
drivers/gpu/drm/i915/display/intel_display.c | 12 +++---
.../drm/i915/display/intel_display_debugfs.c | 2 +-
.../drm/i915/display/intel_display_power.c | 14 +++----
drivers/gpu/drm/i915/display/intel_dp.c | 9 +++--
.../drm/i915/display/intel_dp_aux_backlight.c | 2 +-
drivers/gpu/drm/i915/display/intel_fbc.c | 12 +++---
drivers/gpu/drm/i915/display/intel_lvds.c | 4 +-
drivers/gpu/drm/i915/display/intel_opregion.c | 2 +-
drivers/gpu/drm/i915/display/intel_panel.c | 4 +-
drivers/gpu/drm/i915/display/intel_psr.c | 6 +--
drivers/gpu/drm/i915/gem/i915_gem_context.c | 4 +-
.../gpu/drm/i915/gt/intel_engine_heartbeat.c | 3 +-
drivers/gpu/drm/i915/gt/intel_reset.c | 6 +--
.../drm/i915/gt/selftest_engine_heartbeat.c | 6 +--
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c | 15 ++++---
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 +-
drivers/gpu/drm/i915/gt/uc/intel_uc.c | 20 +++++-----
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 22 +++++-----
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
drivers/gpu/drm/i915/i915_debugfs_params.c | 2 +-
drivers/gpu/drm/i915/i915_drv.c | 9 ++++-
drivers/gpu/drm/i915/i915_drv.h | 5 ++-
drivers/gpu/drm/i915/i915_getparam.c | 2 +-
drivers/gpu/drm/i915/i915_gpu_error.c | 4 +-
drivers/gpu/drm/i915/i915_params.c | 40 ++++++++++++-------
drivers/gpu/drm/i915/i915_params.h | 2 +-
drivers/gpu/drm/i915/intel_gvt.c | 8 ++--
drivers/gpu/drm/i915/intel_region_lmem.c | 6 +--
drivers/gpu/drm/i915/intel_uncore.c | 8 ++--
32 files changed, 140 insertions(+), 111 deletions(-)
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-04-07 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 9:49 Jani Nikula [this message]
2020-04-07 9:49 ` [Intel-gfx] [PATCH 1/3] drm/i915/params: don't expose inject_probe_failure in debugfs Jani Nikula
2020-04-07 9:49 ` [Intel-gfx] [PATCH 2/3] drm/i915/params: prevent changing module params runtime Jani Nikula
2020-04-07 9:49 ` [Intel-gfx] [PATCH 3/3] drm/i915/params: switch to device specific parameters Jani Nikula
2020-04-07 12:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: from module params to device params (rev2) Patchwork
2020-04-07 12:43 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=cover.1586252867.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=juha-pekka.heikkila@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;
as well as URLs for NNTP newsgroup(s).