From: Peng Fan <peng.fan@oss.nxp.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Peng Fan <peng.fan@nxp.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, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] firmware: arm_scmi: imx: Add documentation for MISC_BOARD_INFO
Date: Sun, 31 Aug 2025 16:15:41 +0800 [thread overview]
Message-ID: <20250831081541.GA17728@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <20250829-handsome-fast-clam-a35afd@sudeepholla>
On Fri, Aug 29, 2025 at 11:43:41AM +0100, Sudeep Holla wrote:
>On Wed, Aug 27, 2025 at 12:59:13PM +0800, Peng Fan wrote:
>> System Manager Firmware supports getting board information, add
>> documentation for this API
>
>s/API/MISC_BOARD_INFO command/
>
Fix in V4.
>>
>> +protocol_id: 0x84
>> +
>> ++--------------------+---------------------------------------------------------+
>> +|Return values |
>> ++--------------------+---------------------------------------------------------+
>> +|Name |Description |
>> ++--------------------+---------------------------------------------------------+
>> +|int32 status |SUCCESS: config name return |
>> +| |NOT_SUPPORTED: name not available |
>> ++--------------------+---------------------------------------------------------+
>> +|uint32 attributes |Board specific attributes reserved for future expansion |
>> +| |without breaking backwards compatibility |
>
>Is 0 the expected value in this version of the spec as it is just reserved ?
>Please state the same explicitly here.
Yes. The SM firmware set it 0 by default.
I will add "The firmware set the value to 0 for now".
Thanks,
Peng
>
>--
>Regards,
>Sudeep
next prev parent reply other threads:[~2025-08-31 7:04 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 [this message]
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
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=20250831081541.GA17728@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®