From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Pankaj Gupta <pankaj.gupta@nxp.com>,
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>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v25 3/7] firmware: imx: add driver for NXP EdgeLock Enclave
Date: Tue, 24 Feb 2026 12:16:56 +0100 [thread overview]
Message-ID: <0e1dab92-b4a3-4450-be59-32df5849b5ef@kontron.de> (raw)
In-Reply-To: <20260122-imx-se-if-v25-3-5c3e3e3b69a8@nxp.com>
On 22.01.26 12:49, Pankaj Gupta wrote:
> Add MU-based communication interface for secure enclave.
>
> NXP hardware IP(s) for secure-enclaves like Edgelock Enclave(ELE), are
> embedded in the SoC to support the features like HSM, SHE & V2X, using
> message based communication interface.
>
> The secure enclave FW communicates with Linux over single or multiple
> dedicated messaging unit(MU) based interface(s).
> Exists on i.MX SoC(s) like i.MX8ULP, i.MX93, i.MX95 etc.
>
> For i.MX9x SoC(s) there is at least one dedicated ELE MU(s) for each
> world - Linux(one or more) and OPTEE-OS (one or more).
>
> Other dependent kernel drivers will be:
> - NVMEM: that supports non-volatile devices like EFUSES,
> managed by NXP's secure-enclave.
>
> Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
Reviewed-by: Frieder Schrempf <frieder.schrempf@kontron.de>
next prev parent reply other threads:[~2026-02-24 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 11:49 [PATCH v25 0/7] firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 1/7] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 3/7] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2026-02-24 10:49 ` Frieder Schrempf
2026-02-24 11:16 ` Frieder Schrempf [this message]
2026-01-22 11:49 ` [PATCH v25 4/7] firmware: imx: device context dedicated to priv Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 5/7] firmware: drivers: imx: adds miscdev Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 6/7] arm64: dts: imx8ulp: add secure enclave node Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 7/7] arm64: dts: imx8ulp-evk: add reserved memory property Pankaj Gupta
2026-01-29 16:58 ` [PATCH v25 0/7] firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2026-02-24 11:18 ` Frieder Schrempf
2026-04-21 7:52 ` Frieder Schrempf
2026-04-21 8:57 ` Frank Li
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=0e1dab92-b4a3-4450-be59-32df5849b5ef@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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=pankaj.gupta@nxp.com \
--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