From: Jagath Jog J <jagathjog1996@gmail.com>
To: mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, mcanal@igalia.com,
maarten.lankhorst@linux.intel.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
jagathjog1996@gmail.com
Subject: [RFC 0/1] drm/mipi-dbi: Use drm_device for debugfs, drop drm_minor
Date: Mon, 21 Apr 2025 14:29:06 +0530 [thread overview]
Message-ID: <20250421085907.24972-1-jagathjog1996@gmail.com> (raw)
This patch updates the MIPI DBI driver to use drm_device.debugfs_root
instead of drm_minor for creating debugfs files. The debugfs setup is now
done earlier in probe(), before drm_dev_register(), and the drivers can
avoid using the .debugfs_init callback.
This is an initial version, and only a few drivers are updated for now.
I noticed that some newer drivers or patches still use
drm_debugfs_create_files(), which relies on drm_minor. I was wondering if
there is a specific reason for this, or if there's a plan to switch to
drm_debugfs_add_files? I can send patches to update more drivers if
that helps.
This patch helps move toward the debugfs cleanup task listed here:
https://docs.kernel.org/gpu/todo.html#clean-up-the-debugfs-support
Looking forward to your feedback.
Jagath Jog J (1):
drm/mipi-dbi: Use drm_device for debugfs, drop drm_minor and
.debugfs_init
drivers/gpu/drm/drm_mipi_dbi.c | 8 ++++----
drivers/gpu/drm/tiny/ili9163.c | 3 ++-
drivers/gpu/drm/tiny/panel-mipi-dbi.c | 3 ++-
include/drm/drm_mipi_dbi.h | 4 ++--
4 files changed, 10 insertions(+), 8 deletions(-)
--
2.20.1
next reply other threads:[~2025-04-21 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 8:59 Jagath Jog J [this message]
2025-04-21 8:59 ` [RFC 1/1] drm/mipi-dbi: Use drm_device for debugfs, drop drm_minor and .debugfs_init Jagath Jog J
2025-04-21 10:29 ` Dmitry Baryshkov
2025-04-22 15:25 ` Jagath Jog J
2025-04-23 10:51 ` [RFC 0/1] drm/mipi-dbi: Use drm_device for debugfs, drop drm_minor Maíra Canal
2025-04-24 6:26 ` Jagath Jog J
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=20250421085907.24972-1-jagathjog1996@gmail.com \
--to=jagathjog1996@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®