intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Brahmajit Das <listout@listout.xyz>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-next@vger.kernel.org
Cc: jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
	joonas.lahtinen@linux.intel.com, tursulin@ursulin.net,
	simona@ffwll.ch
Subject: [RFC PATCH 1/2] drm/i915/debugfs: use new debugfs device-centered functions
Date: Sat,  9 Aug 2025 04:22:25 +0530	[thread overview]
Message-ID: <20250808225226.30465-2-listout@listout.xyz> (raw)
In-Reply-To: <20250808225226.30465-1-listout@listout.xyz>

Replace the use of drm_debugfs_create_files() with the new
drm_debugfs_add_files() function, which centers the debugfs files
management on the drm_device instead of drm_minor.

Signed-off-by: Brahmajit Das <listout@listout.xyz>
---
 drivers/gpu/drm/i915/i915_debugfs.c | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index 967c0501e91e..4c3065d3aca3 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -699,7 +699,7 @@ static const struct file_operations i915_forcewake_fops = {
 	.release = i915_forcewake_release,
 };
 
-static const struct drm_info_list i915_debugfs_list[] = {
+static const struct drm_debugfs_info i915_debugfs_list[] = {
 	{"i915_capabilities", i915_capabilities, 0},
 	{"i915_gem_objects", i915_gem_object_info, 0},
 	{"i915_frequency_info", i915_frequency_info, 0},
@@ -737,9 +737,8 @@ void i915_debugfs_register(struct drm_i915_private *dev_priv)
 				    i915_debugfs_files[i].fops);
 	}
 
-	drm_debugfs_create_files(i915_debugfs_list,
-				 ARRAY_SIZE(i915_debugfs_list),
-				 minor->debugfs_root, minor);
+	drm_debugfs_add_files(minor->dev, i915_debugfs_list,
+			      ARRAY_SIZE(i915_debugfs_list));
 
 	i915_gpu_error_debugfs_register(dev_priv);
 }
-- 
2.50.1


  reply	other threads:[~2025-08-11 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 22:52 [RFC PATCH 0/2] use new debugfs device-centered functions Brahmajit Das
2025-08-08 22:52 ` Brahmajit Das [this message]
2025-08-08 22:52 ` [RFC PATCH 2/2] drm/i915: " Brahmajit Das
2025-08-11 10:23 ` [RFC PATCH 0/2] " Jani Nikula
2025-08-11 13:11   ` Brahmajit Das
2025-08-11 13:11     ` [RFC PATCH 1/2] drm/i915/debugfs: " Brahmajit Das
2025-08-11 13:11     ` [RFC PATCH 2/2] drm/i915: " Brahmajit Das
2025-08-11 13:17   ` [RFC PATCH 0/2] " Brahmajit Das
2025-08-11 13:17     ` [RFC PATCH v2 1/2] drm/i915/debugfs: " Brahmajit Das
2025-08-11 13:17     ` [RFC PATCH v2 2/2] drm/i915: " Brahmajit Das
2025-08-11 14:27   ` ✗ LGCI.VerificationFailed: failure for series starting with [RFC,1/2] drm/i915/debugfs: " Patchwork
2025-08-13 10:44   ` ✗ i915.CI.BAT: failure for series starting with [RFC,1/2] drm/i915/debugfs: use new debugfs device-centered functions (rev2) Patchwork
2025-08-11 13:49 ` ✗ LGCI.VerificationFailed: failure for use new debugfs device-centered functions 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=20250808225226.30465-2-listout@listout.xyz \
    --to=listout@listout.xyz \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-next@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    /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).