From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: "quic_jhugo@quicinc.com" <quic_jhugo@quicinc.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"ogabbay@kernel.org" <ogabbay@kernel.org>,
"mcanal@igalia.com" <mcanal@igalia.com>,
"mwen@igalia.com" <mwen@igalia.com>,
Tomer Tayar <ttayar@habana.ai>,
"maxime@cerno.tech" <maxime@cerno.tech>,
"wambui.karugax@gmail.com" <wambui.karugax@gmail.com>
Subject: Re: [PATCH 2/5] drm/debugfs: rework debugfs directory creation v3
Date: Mon, 17 Apr 2023 12:26:24 +0200 [thread overview]
Message-ID: <20230417102624.GB3141290@linux.intel.com> (raw)
In-Reply-To: <5446881a-bdb8-4d85-bf00-c54e001661f1@gmail.com>
On Mon, Apr 17, 2023 at 09:18:31AM +0200, Christian König wrote:
>
>
> Am 16.04.23 um 18:03 schrieb Tomer Tayar:
> > On 12/04/2023 17:52, Christian König wrote:
> > > /**
> > > - * accel_debugfs_init() - Initialize debugfs for accel minor
> > > + * accel_debugfs_init() - Register debugfs for accel minor
> > > + * @dev: Pointer to the device instance.
> > > + *
> > > + * This function creates a root directory for the device in debugfs.
> > > + */
> > > +void accel_debugfs_init(struct drm_device *dev)
> > > +{
> > > + drm_debugfs_dev_init(dev, accel_debugfs_root);
> > > +}
> > > +
> > > +/**
> > > + * accel_debugfs_register() - Register debugfs for device
> > > * @minor: Pointer to the drm_minor instance.
> > > * @minor_id: The minor's id
> > > *
> > > - * This function initializes the drm minor's debugfs members and creates
> > > - * a root directory for the minor in debugfs. It also creates common files
> > > - * for accelerators and calls the driver's debugfs init callback.
> > > + * Creates common files for accelerators.
> > > */
> > > -void accel_debugfs_init(struct drm_minor *minor, int minor_id)
> > > +void accel_debugfs_register(struct drm_device *dev)
> > > {
I wonder if we need this and can not use drm_debugfs_dev_register() ?
In drm there are two additional files "clients" and "gem_names" which are
appropriate to accel as well and so far we do not have any accel
specific files.
Regards
Stanislaw
next prev parent reply other threads:[~2023-04-17 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 14:52 DRM debugfs cleanup take 4 Christian König
2023-04-12 14:52 ` [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2 Christian König
2023-04-12 14:52 ` [PATCH 2/5] drm/debugfs: rework debugfs directory creation v3 Christian König
2023-04-13 11:29 ` kernel test robot
2023-04-13 15:39 ` kernel test robot
2023-04-16 16:03 ` Tomer Tayar
2023-04-17 7:18 ` Christian König
2023-04-17 10:26 ` Stanislaw Gruszka [this message]
2023-04-24 12:17 ` Christian König
2023-04-12 14:52 ` [PATCH 3/5] drm/debugfs: remove dev->debugfs_list and debugfs_mutex v2 Christian König
2023-04-12 15:11 ` Daniel Vetter
2023-04-13 9:34 ` Christian König
2023-04-13 13:45 ` Daniel Vetter
2023-04-12 14:52 ` [PATCH 4/5] drm/debugfs: rework drm_debugfs_create_files implementation Christian König
2023-04-12 14:52 ` [PATCH 5/5] drm/debugfs: remove debugfs_root pointer from minor Christian König
2023-06-01 15:59 ` DRM debugfs cleanup take 4 Oded Gabbay
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=20230417102624.GB3141290@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=mcanal@igalia.com \
--cc=mwen@igalia.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=ttayar@habana.ai \
--cc=wambui.karugax@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.