> -----邮件原件----- > 发件人: Marek Vasut <[email protected]> > 发送时间: 2025年3月4日 10:58 > 收件人: Alice Guo (OSS) <[email protected]>; [email protected]; > [email protected]; [email protected]; dl-uboot-imx <[email protected]>; > [email protected]; [email protected]; [email protected]; > [email protected] > 抄送: [email protected]; Peng Fan <[email protected]>; Viorel Suman > <[email protected]>; Ye Li <[email protected]> > 主题: Re: 回复: [PATCH v1] mailbox: add i.MX Messaging Unit (MU) driver > > On 3/4/25 3:35 AM, Alice Guo (OSS) wrote: > > [...] > > >>> +static const struct udevice_id ids[] = { > >>> + { .compatible = "fsl,imx6sx-mu", .data = > (ulong)&imx_mu_cfg_imx6sx }, > >>> + { .compatible = "fsl,imx7ulp-mu", .data = > (ulong)&imx_mu_cfg_imx7ulp }, > >>> + { .compatible = "fsl,imx8ulp-mu", .data = > (ulong)&imx_mu_cfg_imx8ulp }, > >>> + { .compatible = "fsl,imx95-mu", .data = (ulong)&imx_mu_cfg_imx95 > >>> +}, > >> Wouldn't it be useful to include also fsl,imx95-mu-ele and > >> fsl,imx95-mu-v2x for > >> iMX95 ? Esp. the ELE is something which surely is present due to the > >> AHAB container, right ? > > > > The compatible " fsl,imx8ulp-mu" used by i.MX8ULP MU is incorrect. Will > modify it in the next version. > > OK > > > The driver of i.MX95 ELE MU is in drivers/misc/imx_ele/ele_mu.c. > > Why does Linux use MU driver for the ELE , while U-Boot has some separate > driver ?
In drivers/firmware/scmi/mailbox_agent.c, some APIs provided by common mailbox framework are used. So, the driver of i.MX 95 MU for SCMI exchanges needs to use common mailbox framework. In drivers/misc/imx_ele/ele_api.c, APIs provided by drivers/misc/misc-uclass.c are used. So, the driver of i.MX MU for ELE needs to use UCLASS_MISC. > > No need to add the driver for i.MX95 MU V2X in U-Boot. > > How so ? Because we do not use i.MX95 MU V2X in U-Boot.
