DMA Engine development
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@kernel.org>
To: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>
Cc: dmaengine@vger.kernel.org
Subject: [PATCH] dmaengine: pl08x: Create debugfs stats file under device folder
Date: Fri, 24 Jul 2026 00:17:39 +0300	[thread overview]
Message-ID: <20260723211739.289699-1-vz@kernel.org> (raw)

If parent folder for a debug file is not set, then this file is created
right in top debugfs mountpoint directory, which is undesired. However
for every DMA controller device its dedicated folder below 'dmaengine'
is created by dma_async_device_register(), and this particular folder
is expected to store all device specific debug files.

The new name "stats" is selected as the most popular debugfs file name
found in other DMA controller device drivers, and the macro constant
for file mode is replaced by the octal value.

Signed-off-by: Vladimir Zapolskiy <vz@kernel.org>
---
 drivers/dma/amba-pl08x.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
index 5e88fd44812d..543c2eb8cfa8 100644
--- a/drivers/dma/amba-pl08x.c
+++ b/drivers/dma/amba-pl08x.c
@@ -2500,8 +2500,8 @@ DEFINE_SHOW_ATTRIBUTE(pl08x_debugfs);
 static void init_pl08x_debugfs(struct pl08x_driver_data *pl08x)
 {
 	/* Expose a simple debugfs interface to view all clocks */
-	debugfs_create_file(dev_name(&pl08x->adev->dev), S_IFREG | S_IRUGO,
-			    NULL, pl08x, &pl08x_debugfs_fops);
+	debugfs_create_file("stats", 0444, pl08x->memcpy.dbg_dev_root,
+			    pl08x, &pl08x_debugfs_fops);
 }
 
 #else
-- 
2.51.0


             reply	other threads:[~2026-07-23 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 21:17 Vladimir Zapolskiy [this message]
2026-07-23 21:30 ` [PATCH] dmaengine: pl08x: Create debugfs stats file under device folder sashiko-bot

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=20260723211739.289699-1-vz@kernel.org \
    --to=vz@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=vkoul@kernel.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