From: Krzysztof Kozlowski <krzk@kernel.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>
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,
Conor Dooley <conor@kernel.org>
Subject: Re: [PATCH v12 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc
Date: Mon, 20 Jan 2025 13:16:30 +0100 [thread overview]
Message-ID: <6110fd00-c050-4bcf-8971-674bc8c0bfc7@kernel.org> (raw)
In-Reply-To: <20250120-imx-se-if-v12-2-c5ec9754570c@nxp.com>
On 20/01/2025 17:52, Pankaj Gupta wrote:
> The NXP security hardware IP(s) like: i.MX EdgeLock Enclave, V2X etc.,
> creates an embedded secure enclave within the SoC boundary to enable
> features like:
> - HSM
> - SHE
> - V2X
>
> Secure-Enclave(s) communication interface are typically via message
> unit, i.e., based on mailbox linux kernel driver. This driver enables
> communication ensuring well defined message sequence protocol between
> Application Core and enclave's firmware.
>
> Driver configures multiple misc-device on the MU, for multiple
> user-space applications, to be able to communicate over single MU.
>
> It exists on some i.MX processors. e.g. i.MX8ULP, i.MX93 etc.
>
> Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Reviewed-by: Conor Dooley <conor@kernel.org>
Where Conor's review tag was actually given?
I don't see any hints in the changelog.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-20 12:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 16:52 [PATCH v12 0/5] Changes in v12: Pankaj Gupta
2025-01-20 11:39 ` [PATCH v12 0/5] Changes in v12: firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2025-01-20 16:52 ` [PATCH v12 1/5] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2025-03-04 11:09 ` Ivan T. Ivanov
2025-01-20 16:52 ` [PATCH v12 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2025-01-20 12:16 ` Krzysztof Kozlowski [this message]
2025-01-20 13:07 ` [EXT] " Pankaj Gupta
2025-01-20 15:01 ` Krzysztof Kozlowski
2025-01-22 10:35 ` Krzysztof Kozlowski
2025-01-22 18:26 ` Conor Dooley
2025-01-22 19:46 ` Frank Li
2025-01-22 10:37 ` Krzysztof Kozlowski
2025-01-20 16:52 ` [PATCH v12 3/5] arm64: dts: imx8ulp-evk: add nxp secure enclave firmware Pankaj Gupta
2025-01-20 16:52 ` [PATCH v12 4/5] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2025-01-20 12:23 ` Krzysztof Kozlowski
2025-01-22 11:13 ` [EXT] " Pankaj Gupta
2025-01-22 11:23 ` Krzysztof Kozlowski
2025-01-22 12:55 ` Pankaj Gupta
2025-01-22 12:57 ` Krzysztof Kozlowski
2025-01-20 19:43 ` kernel test robot
2025-01-20 16:52 ` [PATCH v12 5/5] firmware: imx: adds miscdev 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=6110fd00-c050-4bcf-8971-674bc8c0bfc7@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@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