devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: pankaj.gupta@oss.nxp.com, Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Pankaj Gupta <pankaj.gupta@nxp.com>,
	Randy Dunlap <rdunlap@infradead.org>
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
Subject: Re: [PATCH v50 3/7] firmware: imx: add driver for NXP EdgeLock Enclave
Date: Mon, 14 Sep 2026 12:47:38 +0200	[thread overview]
Message-ID: <9d1fb5e5-e0ad-4fbb-83ee-5f267db4f030@kontron.de> (raw)
In-Reply-To: <2062655f-886d-4194-b7bf-3048b7139c7f@kontron.de>

On 14.09.26 12:45, Frieder Schrempf wrote:
> On 12.09.26 19:03, pankaj.gupta@oss.nxp.com wrote:
>> From: Pankaj Gupta <pankaj.gupta@nxp.com>
>>
>> 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>
>> Tested-by: Frieder Schrempf <frieder.schrempf@kontron.de>
> 
> My review was for v25, my test was valid for v29. We are now at v50, so
> please, as requested before, drop the tags as I don't think they can be
> considered to be still valid with all these changes.
Sorry, I missed that you already removed the R-b in the meantime. But I
guess the T-b should also go. Please ping me when all the problems in
the code are solved and I will test once more.

  parent reply	other threads:[~2026-09-14 10:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 17:03 [PATCH v50 0/7] firmware: imx: driver for NXP secure-enclave pankaj.gupta
2026-09-12 17:03 ` [PATCH v50 1/7] Documentation/firmware: add imx/se to other_interfaces pankaj.gupta
2026-09-12 11:44   ` sashiko-bot
2026-09-12 17:03 ` [PATCH v50 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc pankaj.gupta
2026-09-12 11:45   ` sashiko-bot
2026-09-12 17:03 ` [PATCH v50 3/7] firmware: imx: add driver for NXP EdgeLock Enclave pankaj.gupta
2026-09-12 11:46   ` sashiko-bot
2026-09-14 10:45   ` Frieder Schrempf
2026-09-14 10:47     ` [EXT] " Pankaj Gupta
2026-09-14 10:47     ` Frieder Schrempf [this message]
2026-09-12 17:03 ` [PATCH v50 4/7] firmware: imx: device context dedicated to priv pankaj.gupta
2026-09-12 17:03 ` [PATCH v50 5/7] firmware: imx: adds miscdev pankaj.gupta
2026-09-12 11:48   ` sashiko-bot
2026-09-12 12:04     ` Pankaj Gupta (OSS)
2026-09-12 17:03 ` [PATCH v50 6/7] arm64: dts: imx8ulp: add secure enclave node pankaj.gupta
2026-09-12 11:45   ` sashiko-bot
2026-09-12 17:03 ` [PATCH v50 7/7] arm64: dts: imx8ulp: add reserved memory for EdgeLock Enclave pankaj.gupta

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=9d1fb5e5-e0ad-4fbb-83ee-5f267db4f030@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=pankaj.gupta@oss.nxp.com \
    --cc=rdunlap@infradead.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).