From: Peng Fan <peng.fan@oss.nxp.com>
To: Peng Fan <peng.fan@nxp.com>, Sudeep Holla <sudeep.holla@arm.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" <arm-scmi@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 5/6] firmware: arm_scmi: imx: Support getting syslog of MISC protocol
Date: Tue, 9 Sep 2025 12:01:59 +0800 [thread overview]
Message-ID: <20250909040159.GC20475@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <PAXPR04MB845929E7106141E785A32387880CA@PAXPR04MB8459.eurprd04.prod.outlook.com>
Hi Sudeep,
On Mon, Sep 08, 2025 at 11:51:02AM +0000, Peng Fan wrote:
>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.
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.
I will post out the patch for 5 an 6 later this week.
Thanks,
Peng
>
>Thanks,
>Peng
>
next prev parent reply other threads:[~2025-09-09 2:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 10:40 [PATCH v4 0/6] firmware: arm_scmi: imx: Dump syslog and system_info Peng Fan
2025-09-04 10:40 ` [PATCH v4 1/6] firmware: arm_scmi: imx: Add documentation for MISC_BOARD_INFO Peng Fan
2025-09-04 10:40 ` [PATCH v4 2/6] firmware: arm_scmi: imx: Support discovering buildinfo of MISC protocol Peng Fan
2025-09-04 10:40 ` [PATCH v4 3/6] firmware: arm_scmi: imx: Support getting cfg info " Peng Fan
2025-09-04 10:40 ` [PATCH v4 4/6] firmware: arm_scmi: imx: Support getting board " Peng Fan
2025-09-04 10:40 ` [PATCH v4 5/6] firmware: arm_scmi: imx: Support getting syslog " Peng Fan
2025-09-08 11:04 ` Sudeep Holla
2025-09-08 11:51 ` Peng Fan
2025-09-09 4:01 ` Peng Fan [this message]
2025-09-09 8:58 ` Sudeep Holla
2025-09-11 11:15 ` Peng Fan
2025-09-12 10:28 ` Sudeep Holla
2025-09-04 10:40 ` [PATCH v4 6/6] firmware: imx: sm-misc: Dump syslog info Peng Fan
2025-09-08 11:07 ` Sudeep Holla
2025-09-08 11:09 ` [PATCH v4 0/6] firmware: arm_scmi: imx: Dump syslog and system_info Sudeep Holla
2025-09-08 11:53 ` Peng Fan
2025-09-09 10:32 ` (subset) " Sudeep Holla
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=20250909040159.GC20475@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.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
all inboxes | Powered by JetHome®