Hi Daniel,
As discussed already on your query, answering to this, for everybody:
There is no existing NXP MU driver, that is up-streamed.
ele-mu driver is using(dependent on) the underline IMX_MBOX, driver you might be referring to.
Thanks.
Regards
Pankaj
> -----Original Message-----
> From: Daniel Baluta <daniel.baluta@gmail.com>
> Sent: Monday, April 24, 2023 7:38 PM
> To: Pankaj Gupta <pankaj.gupta@nxp.com>
> Cc: shawnguo@kernel.org; s.hauer@pengutronix.de;
> kernel@pengutronix.de; festevam@gmail.com; dl-linux-imx <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 <gaurav.jain@nxp.com>; Sahil
> Malhotra <sahil.malhotra@nxp.com>; Aisheng Dong
> <aisheng.dong@nxp.com>; Varun Sethi <V.Sethi@nxp.com>
> Subject: [EXT] Re: [PATCH v2 0/7] *** firmware: imx: NXP Edgelock Enclave
> MUAP Driver ***
>
> Caution: EXT Email
>
> On Wed, Apr 19, 2023 at 3:45 PM 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 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?