diff options
| author | Pankaj Gupta <pankaj.gupta@nxp.com> | 2026-09-15 01:09:59 +0530 |
|---|---|---|
| committer | Frank Li <Frank.Li@nxp.com> | 2026-09-23 17:16:39 -0400 |
| commit | 1af212aacb3f6a33106cfd86a50acda47c65b034 (patch) | |
| tree | 96bfbfd6103de40c31631a76f14917fbe1b86232 /drivers/firmware/imx/se_ctrl.c | |
| parent | 92108b234bfa39f97335f7f635ac49d5ecea5e82 (diff) | |
| download | linux-next-1af212aacb3f6a33106cfd86a50acda47c65b034.tar.gz linux-next-1af212aacb3f6a33106cfd86a50acda47c65b034.zip | |
dt-bindings: arm: fsl: add imx-se-fw binding doc
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>
Tested-by: Peng Fan <peng.fan@nxp.com> #i.MX8ULP-EVK
Signed-off-by: Frank Li <Frank.Li@nxp.com>
Diffstat (limited to 'drivers/firmware/imx/se_ctrl.c')
0 files changed, 0 insertions, 0 deletions