[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<AM9PR04MB86047F4AE8CF4B56947381D1954BA@AM9PR04MB8604.eurprd04.prod.outlook.com>
Date: Fri, 11 Jul 2025 06:21:33 +0000
From: Pankaj Gupta <pankaj.gupta@....com>
To: Shawn Guo <shawnguo2@...h.net>
CC: Jonathan Corbet <corbet@....net>, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Shawn Guo
<shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix
Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"imx@...ts.linux.dev" <imx@...ts.linux.dev>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, Frank Li <frank.li@....com>
Subject: RE: [EXT] Re: [PATCH v17 0/7] firmware: imx: driver for NXP
secure-enclave
> On Wed, Jul 09, 2025 at 10:23:45AM +0000, Pankaj Gupta wrote:
>>>>> Hi Shawn,
>>>>>
>>>>> To test it on MX93, you need additional patches on top of these.
>>>>>
>>>>> The plan was to send the next patch-set to enable the support for
>>>>> MX93, once these got merged.
>>>>>
>>>>> If you suggest, I can share the patche-set to enable MX93, as an
>>>>> attachment to you only.
>>
>>>> Yes, please. I would like to test the driver before it gets
>>>> merged,
>> thanks!
>>
>>> Please find attached the patches for enabling iMX93.
>>
>>> I have also sent v18 to dispose off the comments:
>>> 1. documentation,
>>> 2. updating the commit message with collected reviewed by tags.
>>
>> Are you able to test the driver on i.MX93?
>> Any help needed?
> I did not expect those additional patches (except i.MX93 DTS
> changes) for testing the series on i.MX93. So, no, I didn't test, sorry!
List of Patches:
0001: is required to call "init_fw" API, for SoC i.XM9x.
0002: i.MX93 do not have CAAM, ELE's RNG needs to be started, post init_fw.
0003: iMX93 do not have CAAM, hence (T)RNG & hwrng, need to enabled via ELE.
0004: enforce message sequence flow to prevent any message exchange out of
sequence. Required by power management API(s).
0005: additional API(s) required by Linux kernel management layers like
NVMEM & power management.
0006: EXPORTED API to be used by other kernel management layers.
0007 & 0008: are DTSI & DTS changes.
1. If you add DTSI & DTS changes, i.MX93 board will come up with driver
successfully probed.
Logs:
root@...93evk:~# dmesg | grep fsl-se
[ 1.414748] fsl-se secure-enclave: assigned reserved memory node
memory@...20000
[ 1.427195] fsl-se secure-enclave: i.MX secure-enclave: hsm0 interface to
firmware, configured.
root@...93evk:~# ele_hsm_test --info
SAB Error: SAB CMD [0x10] Resp [0x1329] - Unknown error code
hsm_open_session failed err:0x13
2. If you want to use ELE test, you need to apply patches: 0001 & 0002.
Logs:
root@...93evk:~# dmesg | grep fsl-se
[ 1.414748] fsl-se secure-enclave: assigned reserved memory node
memory@...20000
[ 1.427195] fsl-se secure-enclave: i.MX secure-enclave: hsm0 interface to
firmware, configured.
root@...93evk:~# ele_hsm_test --info
hsm_open_session PASS 0x376ace9e
-----------------------------------------------------------
Global Info:
-----------------------------------------------------------
i.MX93 A2
Open Lifecycle
Fips mode 0x0
LIB Version: 1.1.1
NVM Version: 1.1.1
Build ID: 4060004597fe1bf9e84ec0804b98d855f1ed0e13
-----------------------------------------------------------
hsm_close_session[0] ret:0x0
> Shawn
Download attachment "smime.p7s" of type "application/pkcs7-signature" (11094 bytes)
Powered by blists - more mailing lists