mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 3/6] firmware: arm_scmi: imx: Support getting cfg info of MISC protocol
Date: Sun, 31 Aug 2025 16:25:03 +0800	[thread overview]
Message-ID: <20250831082503.GD17728@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <20250829-sophisticated-lemon-porcupine-8dffa4@sudeepholla>

On Fri, Aug 29, 2025 at 11:56:15AM +0100, Sudeep Holla wrote:
>On Wed, Aug 27, 2025 at 12:59:15PM +0800, Peng Fan wrote:
>> MISC protocol supports getting the System Manager(SM) mode selection
>> and configuration name. Retrieve the information from SM.
>> 
>> Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
>> Signed-off-by: Peng Fan <peng.fan@nxp.com>
>> ---
>>  .../firmware/arm_scmi/vendors/imx/imx-sm-misc.c    | 35 ++++++++++++++++++++++
>>  1 file changed, 35 insertions(+)
>> 
>> diff --git a/drivers/firmware/arm_scmi/vendors/imx/imx-sm-misc.c b/drivers/firmware/arm_scmi/vendors/imx/imx-sm-misc.c
>> index 464afeae8267d8c1eca4c4d5e008eca6d741c6ff..220b9369fb537306f9e1a105930ad4d65e6b10aa 100644
>> --- a/drivers/firmware/arm_scmi/vendors/imx/imx-sm-misc.c
>> +++ b/drivers/firmware/arm_scmi/vendors/imx/imx-sm-misc.c
>> @@ -26,6 +26,7 @@ enum scmi_imx_misc_protocol_cmd {
>>  	SCMI_IMX_MISC_CTRL_SET	= 0x3,
>>  	SCMI_IMX_MISC_CTRL_GET	= 0x4,
>>  	SCMI_IMX_MISC_DISCOVER_BUILDINFO = 0x6,
>> +	SCMI_IMX_MISC_CFG_INFO = 0xC,
>
>1. Order it by command number
>2. Be consistent with the document, MISC_CFG_INFO_GET is used there.

Fix in V4.

>
>>  	SCMI_IMX_MISC_CTRL_NOTIFY = 0x8,
>>  };
>>  
>> @@ -75,6 +76,12 @@ struct scmi_imx_misc_buildinfo_out {
>>  	u8 buildtime[MISC_MAX_BUILDTIME];
>>  };
>>  
>> +struct scmi_imx_misc_cfg_info_out {
>> +	__le32 msel;
>> +#define MISC_MAX_CFGNAME	16
>> +	u8 cfgname[MISC_MAX_CFGNAME];
>> +};
>> +
>>  static int scmi_imx_misc_attributes_get(const struct scmi_protocol_handle *ph,
>>  					struct scmi_imx_misc_info *mi)
>>  {
>> @@ -309,6 +316,30 @@ static int scmi_imx_misc_discover_build_info(const struct scmi_protocol_handle *
>>  	return ret;
>>  }
>>  
>> +static int scmi_imx_misc_cfg_info(const struct scmi_protocol_handle *ph)
>> +{
>> +	struct scmi_imx_misc_cfg_info_out *out;
>> +	char name[MISC_MAX_CFGNAME];
>> +	struct scmi_xfer *t;
>> +	int ret;
>> +
>> +	ret = ph->xops->xfer_get_init(ph, SCMI_IMX_MISC_CFG_INFO, 0, sizeof(*out), &t);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = ph->xops->do_xfer(ph, t);
>> +	if (!ret) {
>> +		out = t->rx.buf;
>> +		strscpy(name, out->cfgname, MISC_MAX_CFGNAME);
>> +		dev_info(ph->dev, "SM Config\t= %s, mSel = %u\n",
>> +			 name, le32_to_cpu(out->msel));
>> +	}
>> +
>> +	ph->xops->xfer_put(ph, t);
>> +
>> +	return ret;
>> +}
>> +
>>  static const struct scmi_imx_misc_proto_ops scmi_imx_misc_proto_ops = {
>>  	.misc_ctrl_set = scmi_imx_misc_ctrl_set,
>>  	.misc_ctrl_get = scmi_imx_misc_ctrl_get,
>> @@ -340,6 +371,10 @@ static int scmi_imx_misc_protocol_init(const struct scmi_protocol_handle *ph)
>>  	if (ret)
>>  		return ret;
>>  
>> +	ret = scmi_imx_misc_cfg_info(ph);
>
>s/scmi_imx_misc_cfg_info/scmi_imx_misc_cfg_info_get/

Fix in V4.

>
>> +	if (ret)
>
>Again the document hasn't mark it as mandatory, so handle NOT_SUPPORTED
>gracefully.

Yeah,
"if (ret && ret != -EOPNOTSUPP)
	return ret;
"

Thanks,
Peng

>
>-- 
>Regards,
>Sudeep

  reply	other threads:[~2025-08-31  7:13 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 [this message]
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=20250831082503.GD17728@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®