From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>,
quic_carlv@quicinc.com, quic_pkanojiy@quicinc.com,
stanislaw.gruszka@linux.intel.com
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
ogabbay@kernel.org
Subject: Re: [PATCH 2/3] accel/qaic: Add fifo size debugfs
Date: Thu, 14 Mar 2024 12:44:03 +0100 [thread overview]
Message-ID: <a66d528b-e086-434f-9429-2f99352ba6a4@linux.intel.com> (raw)
In-Reply-To: <20240311165826.1728693-3-quic_jhugo@quicinc.com>
Reviewed-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
On 11.03.2024 17:58, Jeffrey Hugo wrote:
> Each DMA Bridge Channel (dbc) has a unique configured fifo size which is
> specified by the userspace client of that dbc. Since the fifo is
> circular, it is useful to know the configured size when debugging
> issues.
>
> Add a per-dbc subdirectory in debugfs and in each subdirectory add a
> fifo_size entry that will display the size of that dbc's fifo when read.
>
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> Reviewed-by: Carl Vanderlip <quic_carlv@quicinc.com>
> Reviewed-by: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
> ---
> drivers/accel/qaic/qaic_debugfs.c | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/drivers/accel/qaic/qaic_debugfs.c b/drivers/accel/qaic/qaic_debugfs.c
> index 4f87fe29be1a..9d56cd451b64 100644
> --- a/drivers/accel/qaic/qaic_debugfs.c
> +++ b/drivers/accel/qaic/qaic_debugfs.c
> @@ -11,6 +11,7 @@
> #include <linux/mutex.h>
> #include <linux/pci.h>
> #include <linux/seq_file.h>
> +#include <linux/sprintf.h>
> #include <linux/string.h>
> #include <linux/types.h>
> #include <linux/workqueue.h>
> @@ -20,6 +21,7 @@
>
> #define BOOTLOG_POOL_SIZE 16
> #define BOOTLOG_MSG_SIZE 512
> +#define QAIC_DBC_DIR_NAME 9
>
> struct bootlog_msg {
> /* Buffer for bootlog messages */
> @@ -74,14 +76,43 @@ static const struct file_operations bootlog_fops = {
> .release = single_release,
> };
>
> +static int read_dbc_fifo_size(struct seq_file *s, void *unused)
> +{
> + struct dma_bridge_chan *dbc = s->private;
> +
> + seq_printf(s, "%u\n", dbc->nelem);
> + return 0;
> +}
> +
> +static int fifo_size_open(struct inode *inode, struct file *file)
> +{
> + return single_open(file, read_dbc_fifo_size, inode->i_private);
> +}
> +
> +static const struct file_operations fifo_size_fops = {
> + .owner = THIS_MODULE,
> + .open = fifo_size_open,
> + .read = seq_read,
> + .llseek = seq_lseek,
> + .release = single_release,
> +};
> +
> void qaic_debugfs_init(struct qaic_drm_device *qddev)
> {
> struct qaic_device *qdev = qddev->qdev;
> struct dentry *debugfs_root;
> + struct dentry *debugfs_dir;
> + char name[QAIC_DBC_DIR_NAME];
> + u32 i;
>
> debugfs_root = to_drm(qddev)->debugfs_root;
>
> debugfs_create_file("bootlog", 0400, debugfs_root, qdev, &bootlog_fops);
> + for (i = 0; i < qdev->num_dbc; ++i) {
> + snprintf(name, QAIC_DBC_DIR_NAME, "dbc%03u", i);
> + debugfs_dir = debugfs_create_dir(name, debugfs_root);
> + debugfs_create_file("fifo_size", 0400, debugfs_dir, &qdev->dbc[i], &fifo_size_fops);
> + }
> }
>
> static struct bootlog_page *alloc_bootlog_page(struct qaic_device *qdev)
next prev parent reply other threads:[~2024-03-14 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 16:58 [PATCH 0/3] accel/qaic: Add debugfs entries Jeffrey Hugo
2024-03-11 16:58 ` [PATCH 1/3] accel/qaic: Add bootlog debugfs Jeffrey Hugo
2024-03-14 11:41 ` Jacek Lawrynowicz
2024-03-15 15:39 ` Jeffrey Hugo
2024-03-18 8:49 ` Jacek Lawrynowicz
2024-03-11 16:58 ` [PATCH 2/3] accel/qaic: Add fifo size debugfs Jeffrey Hugo
2024-03-12 8:45 ` kernel test robot
2024-03-14 11:44 ` Jacek Lawrynowicz [this message]
2024-03-11 16:58 ` [PATCH 3/3] accel/qaic: Add fifo queued debugfs Jeffrey Hugo
2024-03-14 11:44 ` Jacek Lawrynowicz
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=a66d528b-e086-434f-9429-2f99352ba6a4@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_pkanojiy@quicinc.com \
--cc=stanislaw.gruszka@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox