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>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sudeep Holla <sudeep.holla@arm.com>,
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 v4 0/6] firmware: arm_scmi: imx: Dump syslog and system_info
Date: Mon, 8 Sep 2025 12:09:47 +0100 [thread overview]
Message-ID: <20250908-brave-umber-spider-eb68bd@sudeepholla> (raw)
In-Reply-To: <20250904-sm-misc-api-v1-v4-0-0bf10eaabdf1@nxp.com>
On Thu, Sep 04, 2025 at 06:40:41PM +0800, Peng Fan wrote:
> System Manager firmware provides API to dump board, silicon, firmware
> information. It also provides API to dump system sleep, wakeup
> information. So add the interface for Linux to retrieve the information:
>
> patch 1 is to add doc for board information which was missed before.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> Changes in v4:
> - Patch 1: Typo in commit log, state the attribute is set to 0 by firmware
> add NOT SUPPORTED return value for syslog
> - Patch 2: rename to scmi_imx_misc_build_info_discover, add -EOPNOTSUPP check
> - Patch 3: rename to scmi_imx_misc_cfg_info_get, correct command order,
> add -EOPNOTSUPP check.
> - Patch 4: correct command order, add -EOPNOTSUPP check.
I will queue 1-4/6 from this series as it is ready. So repost 5-6/6 when
ready. Also I notices some inconsistency with CONTROL vs CTRL in the code
and document. Please choose either CONTROL or CTRL and use the same
in both document and code for the command names and send a patch to fix
the inconsistency.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-09-08 12:23 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
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 ` Sudeep Holla [this message]
2025-09-08 11:53 ` [PATCH v4 0/6] firmware: arm_scmi: imx: Dump syslog and system_info 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=20250908-brave-umber-spider-eb68bd@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