> -----Original Message----- > From: Jassi Brar [mailto:jassisinghbrar@xxxxxxxxx] > Sent: Thursday, July 26, 2018 8:27 PM > To: A.s. Dong <aisheng.dong@xxxxxxx> > Cc: Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx>; Shawn Guo > <shawnguo@xxxxxxxxxx>; Fabio Estevam <fabio.estevam@xxxxxxx>; Rob > Herring <robh+dt@xxxxxxxxxx>; Mark Rutland <mark.rutland@xxxxxxx>; > Vladimir Zapolskiy <vladimir_zapolskiy@xxxxxxxxxx>; , Sascha Hauer > <kernel@xxxxxxxxxxxxxx>; , linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux- > mediatek@xxxxxxxxxxxxxxxxxxx, srv_heupstream <linux-arm- > kernel@xxxxxxxxxxxxxxxxxxx>; Devicetree List <devicetree@xxxxxxxxxxxxxxx>; > dl-linux-imx <linux-imx@xxxxxxx> > Subject: Re: [PATCH v7 3/6] dt-bindings: mailbox: imx-mu: add generic MU > channel support [...] > > And SCU firmware does use MU in above way specified by reference > manual. > > 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 two > case property. > > > > 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! ��.n��������+%������w��{.n����z�{��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
