[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<PAXPR04MB8459B7B9A42DB387368629608809A@PAXPR04MB8459.eurprd04.prod.outlook.com>
Date: Thu, 11 Sep 2025 11:15:37 +0000
From: Peng Fan <peng.fan@....com>
To: Sudeep Holla <sudeep.holla@....com>, "Peng Fan (OSS)"
<peng.fan@....nxp.com>
CC: Cristian Marussi <cristian.marussi@....com>, Shawn Guo
<shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix
Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>,
"arm-scmi@...r.kernel.org" <arm-scmi@...r.kernel.org>, "imx@...ts.linux.dev"
<imx@...ts.linux.dev>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v4 5/6] firmware: arm_scmi: imx: Support getting syslog of
MISC protocol
Hi Sudeep,
> Subject: Re: [PATCH v4 5/6] firmware: arm_scmi: imx: Support getting
> syslog of MISC protocol
>
> >
> > I checked with firmware owner, this should be using raw dump.
> > The layout would be changed for new platforms.
> >
> > Since this is raw dump, I think debugfs might be preferred.
> >
>
> It can be sysfs, but it can be just one single 4K dump, no more details
> from the kernel than just raw bytes.
Thanks for approving the use of sysfs. However, I've already developed
a patchset based on debugfs, and following a recent internal discussion,
the consensus is to keep this functionality for debugging purposes.
Given that, I'm inclined to continue using debugfs unless there are
any objections.
Thanks,
Peng
>
> --
> Regards,
> Sudeep
Powered by blists - more mailing lists