From: Frank Li <Frank.li@nxp.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
arm-scmi@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] firmware: imx: sm-misc: Dump syslog info
Date: Wed, 10 Sep 2025 11:25:04 -0400 [thread overview]
Message-ID: <aMGYUALGv283tnV7@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250910-sm-syslog-v1-2-5b36f8f21da6@nxp.com>
On Wed, Sep 10, 2025 at 10:28:18PM +0800, Peng Fan wrote:
> Add debugfs interface to read System Manager syslog info
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/firmware/imx/sm-misc.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/drivers/firmware/imx/sm-misc.c b/drivers/firmware/imx/sm-misc.c
> index fc3ee12c2be878e0285183e3381c9514a63d5142..4678d76b7dd6907533b5131c15ff0edcb66f43b2 100644
> --- a/drivers/firmware/imx/sm-misc.c
> +++ b/drivers/firmware/imx/sm-misc.c
> @@ -3,12 +3,15 @@
> * Copyright 2024 NXP
> */
>
> +#include <linux/debugfs.h>
> +#include <linux/device/devres.h>
> #include <linux/firmware/imx/sm.h>
> #include <linux/module.h>
> #include <linux/of.h>
> #include <linux/platform_device.h>
> #include <linux/scmi_protocol.h>
> #include <linux/scmi_imx_protocol.h>
> +#include <linux/seq_file.h>
>
> static const struct scmi_imx_misc_proto_ops *imx_misc_ctrl_ops;
> static struct scmi_protocol_handle *ph;
> @@ -44,10 +47,43 @@ static int scmi_imx_misc_ctrl_notifier(struct notifier_block *nb,
> return 0;
> }
>
> +static int syslog_show(struct seq_file *file, void *priv)
> +{
> + struct device *dev = file->private;
> + /* 4KB is large enough for syslog */
> + void *syslog __free(kfree) = kmalloc(SZ_4K, GFP_KERNEL);
> + /* syslog API use num words, not num bytes */
> + u16 size = SZ_4K / 4;
> + int ret;
> +
> + if (!ph)
> + return -ENODEV;
> +
> + ret = imx_misc_ctrl_ops->misc_syslog(ph, &size, syslog);
> + if (ret) {
> + if (size > SZ_4K / 4) {
> + dev_err(dev, "syslog size is larger than 4KB, please enlarge\n");
> + return ret;
suppose it is never happen, you pass down size to misc_syslog, it should
never write data more than size.
I am not sure what means of misc_syslog() return value. Generally it should
be how many data in pointer 'syslog' if return value > 0.
So seq_hex_dump() should use ret value. Then only dump validate data,
instead of the whole buffer.
Frank
> + }
> + }
> +
> + seq_hex_dump(file, " ", DUMP_PREFIX_NONE, 16, sizeof(u32), syslog, size * 4, false);
> + seq_putc(file, '\n');
> +
> + return 0;
> +}
> +DEFINE_SHOW_ATTRIBUTE(syslog);
> +
> +static void scmi_imx_misc_put(void *p)
> +{
> + debugfs_remove((struct dentry *)p);
> +}
> +
> static int scmi_imx_misc_ctrl_probe(struct scmi_device *sdev)
> {
> const struct scmi_handle *handle = sdev->handle;
> struct device_node *np = sdev->dev.of_node;
> + struct dentry *scmi_imx_dentry;
> u32 src_id, flags;
> int ret, i, num;
>
> @@ -98,6 +134,12 @@ static int scmi_imx_misc_ctrl_probe(struct scmi_device *sdev)
> }
> }
>
> + scmi_imx_dentry = debugfs_create_dir("scmi_imx", NULL);
> + if (!IS_ERR(scmi_imx_dentry))
> + debugfs_create_file("syslog", 0444, scmi_imx_dentry, &sdev->dev, &syslog_fops);
> +
> + devm_add_action_or_reset(&sdev->dev, scmi_imx_misc_put, scmi_imx_dentry);
> +
> return 0;
> }
>
>
> --
> 2.37.1
>
next prev parent reply other threads:[~2025-09-10 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 14:28 [PATCH 0/2] firmware: arm_scmi/imx: Support dump syslog Peng Fan
2025-09-10 14:28 ` [PATCH 1/2] firmware: arm_scmi: imx: Support getting syslog of MISC protocol Peng Fan
2025-09-10 15:17 ` Frank Li
2025-09-11 5:46 ` Peng Fan
2025-09-10 14:28 ` [PATCH 2/2] firmware: imx: sm-misc: Dump syslog info Peng Fan
2025-09-10 15:25 ` Frank Li [this message]
2025-09-12 7:50 ` Peng Fan
2025-09-10 16:10 ` Dan Carpenter
2025-09-11 5:47 ` Peng Fan
2025-09-12 0:08 ` kernel test robot
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=aMGYUALGv283tnV7@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.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