From: Randy Dunlap <rdunlap@infradead.org>
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>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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 v4 4/5] firmware: imx: add driver for NXP EdgeLock Enclave
Date: Fri, 5 Jul 2024 13:44:04 -0700 [thread overview]
Message-ID: <318ebc29-df94-495d-b2bc-b24340c3d82a@infradead.org> (raw)
In-Reply-To: <20240705-imx-se-if-v4-4-52d000e18a1d@nxp.com>
On 7/5/24 6:52 AM, Pankaj Gupta wrote:
> diff --git a/drivers/firmware/imx/Kconfig b/drivers/firmware/imx/Kconfig
> index 183613f82a11..56bdca9bd917 100644
> --- a/drivers/firmware/imx/Kconfig
> +++ b/drivers/firmware/imx/Kconfig
> @@ -22,3 +22,15 @@ config IMX_SCU
>
> This driver manages the IPC interface between host CPU and the
> SCU firmware running on M4.
> +
> +config IMX_SEC_ENCLAVE
> + tristate "i.MX Embedded Secure Enclave - EdgeLock Enclave Firmware driver."
> + depends on IMX_MBOX && ARCH_MXC && ARM64
> + default m if ARCH_MXC
> +
> + help
> + It is possible to use APIs exposed by the iMX Secure Enclave HW IP called:
> + - EdgeLock Enclave Firmware (for i.MX8ULP, i.MX93),
> + like base, HSM, V2X & SHE using the SAB protocol via the shared Messaging
> + Unit. This driver exposes these interfaces via a set of file descriptors
> + allowing to configure shared memory, send and receive messages.
The 4 lines above should be indented with one tab + 2 spaces instead of _many_ spaces.
--
~Randy
next prev parent reply other threads:[~2024-07-05 20:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 13:52 [PATCH v4 0/5] Changes in v4: Pankaj Gupta
2024-07-05 13:52 ` [PATCH v4 1/5] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2024-07-05 13:52 ` [PATCH v4 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2024-07-07 12:34 ` Krzysztof Kozlowski
2024-07-08 5:50 ` [EXT] " Pankaj Gupta
2024-07-08 6:16 ` Krzysztof Kozlowski
2024-07-08 11:19 ` Pankaj Gupta
2024-07-08 11:23 ` Krzysztof Kozlowski
2024-07-08 11:54 ` Pankaj Gupta
2024-07-08 12:56 ` Krzysztof Kozlowski
2024-07-05 13:52 ` [PATCH v4 3/5] arm64: dts: imx8ulp-evk: add nxp secure enclave firmware Pankaj Gupta
2024-07-05 13:52 ` [PATCH v4 4/5] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2024-07-05 20:44 ` Randy Dunlap [this message]
2024-07-09 6:16 ` [EXT] " Pankaj Gupta
2024-07-05 13:52 ` [PATCH v4 5/5] firmware: imx: adds miscdev Pankaj Gupta
2024-07-05 20:47 ` Randy Dunlap
2024-07-09 6:11 ` [EXT] " 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=318ebc29-df94-495d-b2bc-b24340c3d82a@infradead.org \
--to=rdunlap@infradead.org \
--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=krzysztof.kozlowski+dt@linaro.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+dt@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;
as well as URLs for NNTP newsgroup(s).