Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pankaj Gupta <pankaj.gupta@nxp.com>
To: Frank Li <frank.li@nxp.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v14 6/6] firmware: drivers: imx: adds miscdev
Date: Wed, 2 Apr 2025 06:19:36 +0000	[thread overview]
Message-ID: <AM9PR04MB860417C363F5FEE2E024DCF595AF2@AM9PR04MB8604.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM9PR04MB8604940F813742ACA6CA307595AC2@AM9PR04MB8604.eurprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

>> diff drivers/firmware/imx/ele_common.c
...
>> +			err = -EPERM;
>> +			goto exit;
>> +		}
>> +	}
>> +	set_se_rcv_msg_timeout(SE_RCV_MSG_LONG_TIMEOUT);

> you set default TIMEMOUT at suspend, but set LONG TIMEOUT here.
> What's happen, if one instance already resumed, and set
SE_RCV_MSG_LONG_TIMEOUT
> the other instance still in suspend, which will wrong use
SE_RCV_MSG_LONG_TIMEOUT.

You are correct. Since the interface is single here. It is not a problem.
For multiple interfaces, It is required to be put in priv structure.
Will update this in v15.

>> +
>> +	err = ele_msg_send_rcv(dev_ctx,
>> +			       tx_msg,
>> +			       cmd_snd_rcv_rsp_info.tx_buf_sz,
>> +			       rx_msg,

>> a/drivers/firmware/imx/se_ctrl.c b/drivers/firmware/imx/se_ctrl.c 
>> index 144a727bbfe0..9dbe866b7b13 100644
>> --- a/drivers/firmware/imx/se_ctrl.c

>> +char *get_se_if_name(u8 se_if_id)
>> +{
>> +	switch (se_if_id) {
>> +	case SE_TYPE_ID_DBG: return SE_TYPE_STR_DBG;
>> +	case SE_TYPE_ID_HSM: return SE_TYPE_STR_HSM;

> If only use once, needn't define macro, just
>	return "dbg".

It will be used multiple times in coming patches.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 11094 bytes --]

      parent reply	other threads:[~2025-04-02  6:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 18:37 [PATCH v14 0/6] v14: firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2025-03-26 15:04 ` Frank Li
2025-03-26 18:37 ` [PATCH v14 1/6] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2025-03-26 18:37 ` [PATCH v14 2/6] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2025-03-26 18:37 ` [PATCH v14 3/6] arm64: dts: imx8ulp-evk: add nxp secure enclave firmware Pankaj Gupta
2025-03-26 15:03   ` Frank Li
2025-03-26 18:38 ` [PATCH v14 4/6] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2025-03-26 15:33   ` Frank Li
2025-04-01 11:51     ` Pankaj Gupta
     [not found]     ` <AM9PR04MB86040127423D0A657103589D95AC2@AM9PR04MB8604.eurprd04.prod.outlook.com>
2025-04-02  6:14       ` Pankaj Gupta
     [not found]     ` <AM9PR04MB86048345C11F8878146AFE9A95AC2@AM9PR04MB8604.eurprd04.prod.outlook.com>
2025-04-02  6:15       ` Pankaj Gupta
     [not found]     ` <AM9PR04MB8604C02C27C8C43FF89B95DC95AC2@AM9PR04MB8604.eurprd04.prod.outlook.com>
2025-04-02  6:15       ` Pankaj Gupta
2025-04-02 21:20         ` Frank Li
2025-04-03  5:02           ` Pankaj Gupta
2025-04-04 16:50             ` Frank Li
2025-03-26 18:38 ` [PATCH v14 5/6] firmware: imx: device context dedicated to priv Pankaj Gupta
2025-03-26 15:34   ` Frank Li
2025-03-26 18:38 ` [PATCH v14 6/6] firmware: drivers: imx: adds miscdev Pankaj Gupta
2025-03-26 16:00   ` Frank Li
     [not found]     ` <AM9PR04MB8604940F813742ACA6CA307595AC2@AM9PR04MB8604.eurprd04.prod.outlook.com>
2025-04-02  6:19       ` Pankaj Gupta [this message]

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=AM9PR04MB860417C363F5FEE2E024DCF595AF2@AM9PR04MB8604.eurprd04.prod.outlook.com \
    --to=pankaj.gupta@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --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