Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230419175538.855493-1-pankaj.gupta@nxp.com>
In-Reply-To: <20230419175538.855493-1-pankaj.gupta@nxp.com>
From:   Daniel Baluta <daniel.baluta@gmail.com>
Date:   Mon, 24 Apr 2023 17:07:50 +0300
Message-ID: <CAEnQRZD4-BofvpLaatbYnw3G7Mrs35ZiZsrRJmjrZA7qY_QbHw@mail.gmail.com>
Subject: Re: [PATCH v2 0/7] *** firmware: imx: NXP Edgelock Enclave MUAP
 Driver ***
To:     Pankaj Gupta <pankaj.gupta@nxp.com>
Cc:     shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de,
        festevam@gmail.com, linux-imx@nxp.com, robh+dt@kernel.org,
        krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
        gaurav.jain@nxp.com, sahil.malhotra@nxp.com, aisheng.dong@nxp.com,
        V.Sethi@nxp.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, Apr 19, 2023 at 3:45=E2=80=AFPM Pankaj Gupta <pankaj.gupta@nxp.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 co=
ntrol)
> through its interfaces.
>
> The NXP i.MX EdgeLock Enclave Message Unit (ELE-MUAP) is specifically tar=
geted
> 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?