[EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as msi controller

[Frank Li]

> -----Original Message-----
> From: Frank Li <frank.li at nxp.com>
> Sent: Monday, August 29, 2022 9:48 AM
> To: Marc Zyngier <maz at kernel.org>; Rob Herring <robh at kernel.org>
> Cc: tglx at linutronix.de; krzysztof.kozlowski+dt at linaro.org;
> shawnguo at kernel.org; s.hauer at pengutronix.de; kw at linux.com;
> bhelgaas at google.com; linux-kernel at vger.kernel.org;
> devicetree at vger.kernel.org; linux-arm-kernel at lists.infradead.org; linux-
> pci at vger.kernel.org; Peng Fan <peng.fan at nxp.com>; Aisheng Dong
> <aisheng.dong at nxp.com>; jdmason at kudzu.us; kernel at pengutronix.de;
> festevam at gmail.com; dl-linux-imx <linux-imx at nxp.com>; kishon at ti.com;
> lorenzo.pieralisi at arm.com; ntb at lists.linux.dev; lznuaa at gmail.com
> Subject: RE: [EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as
> msi controller
> 
> Caution: EXT Email
> 
> > -----Original Message-----
> > From: Marc Zyngier <maz at kernel.org>
> > Sent: Friday, August 26, 2022 4:45 PM
> > To: Frank Li <frank.li at nxp.com>
> > Cc: Rob Herring <robh at kernel.org>; tglx at linutronix.de;
> > krzysztof.kozlowski+dt at linaro.org; shawnguo at kernel.org;
> > s.hauer at pengutronix.de; kw at linux.com; bhelgaas at google.com; linux-
> > kernel at vger.kernel.org; devicetree at vger.kernel.org; linux-arm-
> > kernel at lists.infradead.org; linux-pci at vger.kernel.org; Peng Fan
> > <peng.fan at nxp.com>; Aisheng Dong <aisheng.dong at nxp.com>;
> > jdmason at kudzu.us; kernel at pengutronix.de; festevam at gmail.com; dl-
> linux-
> > imx <linux-imx at nxp.com>; kishon at ti.com; lorenzo.pieralisi at arm.com;
> > ntb at lists.linux.dev; lznuaa at gmail.com
> > Subject: Re: [EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as
> > msi controller
> >
> > Caution: EXT Email
> >
> > On Fri, 26 Aug 2022 19:59:44 +0100,
> > Frank Li <frank.li at nxp.com> wrote:
> > >
> > > > And I stand by my initial request. "a" doesn't convey any sort of
> > > > useful information. Why not "I" and "II", while we're at it? Or
> > > > something even funkier?
> > >
> > > MU spec use term "a" and "b",  user have to map "I" an "II" to
> > > "a" and "b" when read MU spec and code. it is not straightforward.
> > >
> > > I quote a part of spec.
> > > " The MU is connected as a peripheral under the Peripheral bus on both
> > sides-on
> > > the Processor A-side, the Processor A Peripheral Bus, and on the
> Processor
> > B side,
> > > the Processor B Peripheral Bus."
> > >
> > > Rob Herring and Marc Zynginer:
> > > I can change to any name, which you agree both.
> > >
> > > Some options:
> > > 1. "a", "b"
> > > 2. "a-side", "b-side"
> > > 3. "a-facing", "b-facing"
> > > 4. "I", "II"
> >
> > Use the wording indicated in the spec: "processor-a-side", and
> > "processor-b-side". This is what I asked the first place.
> 
> @Rob Herring:  Do you agree this name?

@Rob Herring:  How about "process-a-side"? 
If you agree,  I will resin these patches soon.

Best regards
Frank Li

> 
> [Frank Li]
> 
> >
> >         M.
> >
> > --
> > Without deviation from the norm, progress is not possible.