[PATCH v7 3/6] dt-bindings: mailbox: imx-mu: add generic MU channel support
From: aisheng.dong@nxp.com (A.s. Dong)
Date: 2018-07-26 13:34:34
Also in:
linux-devicetree
-----Original Message----- From: Jassi Brar [mailto:jassisinghbrar at gmail.com] Sent: Thursday, July 26, 2018 8:27 PM To: A.s. Dong <aisheng.dong@nxp.com> Cc: Oleksij Rempel <o.rempel@pengutronix.de>; Shawn Guo [off-list ref]; Fabio Estevam [off-list ref]; Rob Herring [off-list ref]; Mark Rutland [off-list ref]; Vladimir Zapolskiy [off-list ref]; , Sascha Hauer [off-list ref]; , linux-arm-kernel at lists.infradead.org, linux- mediatek at lists.infradead.org, srv_heupstream <linux-arm- kernel at lists.infradead.org>; Devicetree List [off-list ref]; dl-linux-imx [off-list ref] Subject: Re: [PATCH v7 3/6] dt-bindings: mailbox: imx-mu: add generic MU channel support
[...]
quoted
And SCU firmware does use MU in above way specified by referencemanual.quoted
Even from HW point of view, it's still one channel only mailbox. That's why we change the mbox-cells to 0 accordingly to avoid confusing the multi channels users supported in this driver. As per Sasha's request, we're going to support both protocol (SCU and generic M4) in one mailbox driver, that means we need deal with this twocase property.quoted
If we use mbox-cells 1 case for SCU, then the using would be like: mboxes = <&mailbox 0> which is mixed with the normal multi channel users. And we also must state clearly in binding doc that for mbox-cells 1 case for SCU, the cell value must be 0 which is also confusing with Multi channel users. How do you suggest for such case?Let me read the spec and try to see/shine the light :)
Great, many thanks! Regards Dong Aisheng
Cheers!