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@xxxxxxxxx> > Sent: Monday, April 24, 2023 7:38 PM > To: Pankaj Gupta <pankaj.gupta@xxxxxxx> > Cc: shawnguo@xxxxxxxxxx; s.hauer@xxxxxxxxxxxxxx; > kernel@xxxxxxxxxxxxxx; festevam@xxxxxxxxx; dl-linux-imx <linux- > imx@xxxxxxx>; robh+dt@xxxxxxxxxx; krzysztof.kozlowski+dt@xxxxxxxxxx; > linux-kernel@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; > devicetree@xxxxxxxxxxxxxxx; Gaurav Jain <gaurav.jain@xxxxxxx>; Sahil > Malhotra <sahil.malhotra@xxxxxxx>; Aisheng Dong > <aisheng.dong@xxxxxxx>; Varun Sethi <V.Sethi@xxxxxxx> > 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@xxxxxxx> > 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?
