[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PAXPR04MB845929E7106141E785A32387880CA@PAXPR04MB8459.eurprd04.prod.outlook.com>
Date: Mon, 8 Sep 2025 11:51:02 +0000
From: Peng Fan <peng.fan@....com>
To: Sudeep Holla <sudeep.holla@....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
[...]
> > +};
> > +
>
> Much better now. But I am still thinking if this must go to the
> document to make sure it remains ABI and firmware can't reorder the
> as we might have no way to deal with that. That's the reason I was
> asking for raw dump so that you need not put all these details in the
> spec/document.
Let me check with firmware owner whether they would include this
into i.MX SM spec or not.
If no, raw dump would be the choice.
Thanks,
Peng
Powered by blists - more mailing lists