[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEnQRZD4-BofvpLaatbYnw3G7Mrs35ZiZsrRJmjrZA7qY_QbHw@mail.gmail.com>
Date: Mon, 24 Apr 2023 17:07:50 +0300
From: Daniel Baluta <daniel.baluta@...il.com>
To: Pankaj Gupta <pankaj.gupta@....com>
Cc: shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
festevam@...il.com, linux-imx@....com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
gaurav.jain@....com, sahil.malhotra@....com, aisheng.dong@....com,
V.Sethi@....com
Subject: Re: [PATCH v2 0/7] *** firmware: imx: NXP Edgelock Enclave MUAP
Driver ***
On Wed, Apr 19, 2023 at 3:45 PM Pankaj Gupta <pankaj.gupta@....com> wrote:
>
> v2 Changes:
>
> - Fixed Kernel Test Bot issues.
> - Removed ".../devicetree/bindings/mailbox/fsl,muap.txt"
>
> v1:
>
> The Messaging Unit module enables two processing elements within the SoC to
> communicate and coordinate by passing messages (e.g., data, status and control)
> through its interfaces.
>
> The NXP i.MX EdgeLock Enclave Message Unit (ELE-MUAP) is specifically targeted
> for use between application core and Edgelocke Enclave. It allows to send
> messages to the EL Enclave using a shared mailbox.
>
> Patch-set add the ELE-MU kernel driver for exchanging messages with i.MX NXP
> ELE IP; both from:
> - User-Space Applications via character driver.
> - Kernel-space, used by kernel management layers like DM-Crypt.
What's wrong with existing NXP MU driver?
Powered by blists - more mailing lists