From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/2] drm/i915: debugfs device parameters
Date: Thu, 5 Dec 2019 17:43:39 +0200 [thread overview]
Message-ID: <cover.1575560168.git.jani.nikula@intel.com> (raw)
This is based on patches I sent over a year ago, adding device
parameters to debugfs.
This would be the first step, making the debugfs only an alternative
interface to the module parameters. The path forward would be:
* Add debugfs interface to parameters (this patch)
* Modify IGT to use this debugfs param interface if available, falling
back to module param sysfs (for older kernels)
* Make module params read-only
* Make module params the initial values for really device specific
parameters, i.e. duplicate the params struct in dev_priv and have the
debugfs interface modify only that
* Start axing out unnecessary module parameters that can live in debugfs
only
I tested this stuff way back when, this is an untested rebase for
comments.
BR,
Jani.
Jani Nikula (2):
drm/i915/params: add i915 parameters to debugfs
drm/i915/params: support bool values for int and uint params
drivers/gpu/drm/i915/Makefile | 5 +-
drivers/gpu/drm/i915/i915_debugfs.c | 4 +-
drivers/gpu/drm/i915/i915_debugfs_params.c | 247 +++++++++++++++++++++
drivers/gpu/drm/i915/i915_debugfs_params.h | 14 ++
drivers/gpu/drm/i915/i915_params.c | 2 +-
drivers/gpu/drm/i915/i915_params.h | 76 ++++---
6 files changed, 308 insertions(+), 40 deletions(-)
create mode 100644 drivers/gpu/drm/i915/i915_debugfs_params.c
create mode 100644 drivers/gpu/drm/i915/i915_debugfs_params.h
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-12-05 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 15:43 Jani Nikula [this message]
2019-12-05 15:43 ` [Intel-gfx] [PATCH 1/2] drm/i915/params: add i915 parameters to debugfs Jani Nikula
2019-12-05 17:19 ` Tvrtko Ursulin
2019-12-09 9:53 ` Jani Nikula
2020-01-08 14:45 ` Chris Wilson
2020-01-08 15:07 ` Jani Nikula
2020-01-15 10:04 ` Chris Wilson
2020-01-15 10:39 ` Jani Nikula
2020-01-15 13:12 ` Jani Nikula
2019-12-05 15:43 ` [Intel-gfx] [PATCH 2/2] drm/i915/params: support bool values for int and uint params Jani Nikula
2020-01-15 10:05 ` Chris Wilson
2019-12-05 17:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: debugfs device parameters Patchwork
2019-12-05 17:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2019-12-05 17:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-05 23:06 ` [Intel-gfx] ✗ Fi.CI.IGT: 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.1575560168.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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