From: "Rob Herring (Arm)" <robh@kernel.org>
To: Pankaj Gupta <pankaj.gupta@nxp.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
imx@lists.linux.dev, Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v7 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc
Date: Mon, 9 Sep 2024 09:18:50 -0500 [thread overview]
Message-ID: <172589152997.4184616.5889493628960272898.robh@kernel.org> (raw)
In-Reply-To: <20240904-imx-se-if-v7-2-5afd2ab74264@nxp.com>
On Wed, 04 Sep 2024 16:21:18 +0530, 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>
> ---
> .../devicetree/bindings/firmware/fsl,imx-se.yaml | 91 ++++++++++++++++++++++
> 1 file changed, 91 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-09-09 14:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:51 [PATCH v7 0/5] Changes in v7: Pankaj Gupta
2024-09-04 10:51 ` [PATCH v7 1/5] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2024-09-04 10:51 ` [PATCH v7 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2024-09-09 14:18 ` Rob Herring (Arm) [this message]
2024-09-04 10:51 ` [PATCH v7 3/5] arm64: dts: imx8ulp-evk: add nxp secure enclave firmware Pankaj Gupta
2024-09-04 10:51 ` [PATCH v7 4/5] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2024-09-04 15:43 ` Frank Li
2024-09-04 16:14 ` Pankaj Gupta
2024-09-09 12:19 ` Sascha Hauer
2024-09-19 6:43 ` [EXT] " Pankaj Gupta
2024-09-20 12:02 ` Sascha Hauer
2024-09-25 12:00 ` Pankaj Gupta
2024-09-26 9:51 ` Sascha Hauer
2024-10-01 7:49 ` Pankaj Gupta
2024-10-01 10:32 ` Sascha Hauer
2024-10-09 5:15 ` Pankaj Gupta
2024-09-04 10:51 ` [PATCH v7 5/5] firmware: imx: adds miscdev Pankaj Gupta
2024-09-09 12:22 ` Sascha Hauer
2024-09-20 12:04 ` [EXT] " Pankaj Gupta
2024-09-04 15:22 ` [PATCH v7 0/5] Changes in v7: Frank Li
2024-09-04 16:09 ` Pankaj Gupta
2024-09-04 18:31 ` Fabio Estevam
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=172589152997.4184616.5889493628960272898.robh@kernel.org \
--to=robh@kernel.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=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=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