> -----Original Message----- > From: Jassi Brar [mailto:jassisinghbrar@xxxxxxxxx] > Sent: Wednesday, August 1, 2018 5:58 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 v8 2/4] dt-bindings: mailbox: imx-mu: add generic MU > channel support > > On Wed, Aug 1, 2018 at 2:28 PM, A.s. Dong <aisheng.dong@xxxxxxx> wrote: > > Hi Jassi, > > > >> > + The doorbell channels should be used with shared > >> > + memory and > >> protocol > >> > + level acknowledgment if needed. > >> > + > >> I would avoid this. People might get notions that they have to use > >> shmem with doorbell -- a trivial protocol might mean doing some fixed > >> action (like > >> reset) whenever the doorbell rings. > >> > > > > That's right. > > i.MX8 using the general purpose interrupt for peripherals. No shmem > needed. > > e.g. RTC, Watchdog and ON/OFF interrupt. > > > > BTW, this means the peripheral will use mailbox doorbell channels to > > handle Interrupts. Is there such user case in kernel we can refer to? > > > I don't find any publicly in kernel. > It should be simple though. Acquire the RX channel, and populate the > rx_callback() with the "interrupt" handler. Got it. Thanks Regards Dong Aisheng ��.n��������+%������w��{.n����z�{��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
