> -----Original Message----- > From: Jassi Brar [mailto:jassisinghbrar@xxxxxxxxx] > Sent: Monday, July 30, 2018 9:05 PM > To: Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx> > Cc: A.s. Dong <aisheng.dong@xxxxxxx>; , Sascha Hauer > <kernel@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>; ", linux-arm- > kernel"@lists.infradead.org; , linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux- > mediatek@xxxxxxxxxxxxxxxxxxx, srv_heupstream <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 > > On Mon, Jul 30, 2018 at 1:05 PM, Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx> > wrote: > > Hi Aishen, Jassie, > > > > i'm lost in this discussion. Please, as soon as I need to add some > > changes to my patches, notify me. Preferably on top for email. > > > I am ok with however you choose to implement, 8 unidirectional or 4 > bidirectional channels or whatever. > > We just can't have protocol specific s/w modes in the controller drivers. > > The best solution is to fix the SCU firmware. If that is _really_ impossible, I > provided a solution (3 cells work around). If you have a better idea please > feel free to propose and implement that. > > It will also help if you could share the user code of "scu-mode". If there is no > such code (and we know the driver doesn't respect the "scu-mode" property) > why do we even have that binding? Maybe drop it. The initial idea is using mbox-cells value to distinguish which MU mode is used (single chan or multi chans). Regards Dong Aisheng > > thnx. ��.n��������+%������w��{.n����z�{��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
