From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
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 v3 5/6] firmware: arm_scmi: imx: Support getting syslog of MISC protocol
Date: Fri, 29 Aug 2025 12:22:07 +0100 [thread overview]
Message-ID: <20250829-ludicrous-giga-bison-aa8ace@sudeepholla> (raw)
In-Reply-To: <20250827-sm-misc-api-v1-v3-5-82c982c1815a@nxp.com>
On Wed, Aug 27, 2025 at 12:59:17PM +0800, Peng Fan wrote:
[...]
> static int scmi_imx_misc_protocol_init(const struct scmi_protocol_handle *ph)
> diff --git a/include/linux/scmi_imx_protocol.h b/include/linux/scmi_imx_protocol.h
> index 27bd372cbfb142b6acb0b1cf4b82f061529d0d45..6e18920aac56de67d388e985e3305745d3798c3e 100644
> --- a/include/linux/scmi_imx_protocol.h
> +++ b/include/linux/scmi_imx_protocol.h
> @@ -52,6 +52,23 @@ struct scmi_imx_misc_ctrl_notify_report {
> unsigned int flags;
> };
>
> +struct scmi_imx_misc_sys_sleep_rec {
> + u32 sleepentryusec;
> + u32 sleepexitusec;
> + u32 sleepcnt;
> + u32 wakesource;
> + u32 mixpwrstat;
> + u32 mempwrstat;
> + u32 pllpwrstat;
> + u32 syssleepmode;
> + u32 syssleepflags;
> +};
And since the document/spec doesn't cover details on above, better
to add comment for this to explain each of it. How do you ensure
the backward compatibility if you are assigning a structure to a log
buffer that is not so structured the spec/document. Will be end up
with one structure for each version if f/w screws up the structure ?
Can it be a raw dump of man 4KB instead ? Sorry just realised it now.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-08-29 14:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 4:59 [PATCH v3 0/6] firmware: arm_scmi: imx: Dump syslog and system_info Peng Fan
2025-08-27 4:59 ` [PATCH v3 1/6] firmware: arm_scmi: imx: Add documentation for MISC_BOARD_INFO Peng Fan
2025-08-29 10:43 ` Sudeep Holla
2025-08-31 8:15 ` Peng Fan
2025-08-27 4:59 ` [PATCH v3 2/6] firmware: arm_scmi: imx: Support discovering buildinfo of MISC protocol Peng Fan
2025-08-29 10:48 ` Sudeep Holla
2025-08-31 8:20 ` Peng Fan
2025-08-31 8:25 ` Peng Fan
2025-08-29 10:50 ` Sudeep Holla
2025-08-31 8:22 ` Peng Fan
2025-08-27 4:59 ` [PATCH v3 3/6] firmware: arm_scmi: imx: Support getting cfg info " Peng Fan
2025-08-29 10:56 ` Sudeep Holla
2025-08-31 8:25 ` Peng Fan
2025-08-27 4:59 ` [PATCH v3 4/6] firmware: arm_scmi: imx: Support getting board " Peng Fan
2025-08-29 11:00 ` Sudeep Holla
2025-08-27 4:59 ` [PATCH v3 5/6] firmware: arm_scmi: imx: Support getting syslog " Peng Fan
2025-08-29 11:07 ` Sudeep Holla
2025-08-31 8:28 ` Peng Fan
2025-08-29 11:22 ` Sudeep Holla [this message]
2025-08-31 7:43 ` Peng Fan
2025-08-27 4:59 ` [PATCH v3 6/6] firmware: imx: sm-misc: Dump syslog info Peng Fan
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=20250829-ludicrous-giga-bison-aa8ace@sudeepholla \
--to=sudeep.holla@arm.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 \
/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