Messages in this thread | | | From | Frank Li <> | Subject | RE: [EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as msi controller | Date | Thu, 1 Sep 2022 14:39:44 +0000 |
| |
> -----Original Message----- > From: Frank Li <frank.li@nxp.com> > Sent: Monday, August 29, 2022 9:48 AM > To: Marc Zyngier <maz@kernel.org>; Rob Herring <robh@kernel.org> > Cc: tglx@linutronix.de; krzysztof.kozlowski+dt@linaro.org; > shawnguo@kernel.org; s.hauer@pengutronix.de; kw@linux.com; > bhelgaas@google.com; linux-kernel@vger.kernel.org; > devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux- > pci@vger.kernel.org; Peng Fan <peng.fan@nxp.com>; Aisheng Dong > <aisheng.dong@nxp.com>; jdmason@kudzu.us; kernel@pengutronix.de; > festevam@gmail.com; dl-linux-imx <linux-imx@nxp.com>; kishon@ti.com; > lorenzo.pieralisi@arm.com; ntb@lists.linux.dev; lznuaa@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@kernel.org> > > Sent: Friday, August 26, 2022 4:45 PM > > To: Frank Li <frank.li@nxp.com> > > Cc: Rob Herring <robh@kernel.org>; tglx@linutronix.de; > > krzysztof.kozlowski+dt@linaro.org; shawnguo@kernel.org; > > s.hauer@pengutronix.de; kw@linux.com; bhelgaas@google.com; linux- > > kernel@vger.kernel.org; devicetree@vger.kernel.org; linux-arm- > > kernel@lists.infradead.org; linux-pci@vger.kernel.org; Peng Fan > > <peng.fan@nxp.com>; Aisheng Dong <aisheng.dong@nxp.com>; > > jdmason@kudzu.us; kernel@pengutronix.de; festevam@gmail.com; dl- > linux- > > imx <linux-imx@nxp.com>; kishon@ti.com; lorenzo.pieralisi@arm.com; > > ntb@lists.linux.dev; lznuaa@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@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.
| |