From: Marc Zyngier <maz@kernel.org>
To: Frank Li <frank.li@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kw@linux.com" <kw@linux.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Peng Fan <peng.fan@nxp.com>, Aisheng Dong <aisheng.dong@nxp.com>,
"jdmason@kudzu.us" <jdmason@kudzu.us>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>, "kishon@ti.com" <kishon@ti.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"ntb@lists.linux.dev" <ntb@lists.linux.dev>,
"lznuaa@gmail.com" <lznuaa@gmail.com>
Subject: Re: [EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as msi controller
Date: Fri, 26 Aug 2022 22:44:52 +0100 [thread overview]
Message-ID: <87zgfqvfvv.wl-maz@kernel.org> (raw)
In-Reply-To: <PAXPR04MB918607281F6389092924EE6488759@PAXPR04MB9186.eurprd04.prod.outlook.com>
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.
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Frank Li <frank.li@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kw@linux.com" <kw@linux.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Peng Fan <peng.fan@nxp.com>, Aisheng Dong <aisheng.dong@nxp.com>,
"jdmason@kudzu.us" <jdmason@kudzu.us>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>, "kishon@ti.com" <kishon@ti.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"ntb@lists.linux.dev" <ntb@lists.linux.dev>,
"lznuaa@gmail.com" <lznuaa@gmail.com>
Subject: Re: [EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as msi controller
Date: Fri, 26 Aug 2022 22:44:52 +0100 [thread overview]
Message-ID: <87zgfqvfvv.wl-maz@kernel.org> (raw)
In-Reply-To: <PAXPR04MB918607281F6389092924EE6488759@PAXPR04MB9186.eurprd04.prod.outlook.com>
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.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-26 21:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:51 [PATCH v7 0/4] PCI EP driver support MSI doorbell from host Frank Li
2022-08-22 15:51 ` Frank Li
2022-08-22 15:51 ` [PATCH v7 1/4] irqchip: allow pass down .pm field at IRQCHIP_PLATFORM_DRIVER_END Frank Li
2022-08-22 15:51 ` Frank Li
2022-08-22 15:51 ` [PATCH v7 2/4] irqchip: Add IMX MU MSI controller driver Frank Li
2022-08-22 15:51 ` Frank Li
2022-08-22 15:51 ` [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as msi controller Frank Li
2022-08-22 15:51 ` Frank Li
2022-08-25 21:21 ` Rob Herring
2022-08-25 21:21 ` Rob Herring
2022-08-25 21:42 ` [EXT] " Frank Li
2022-08-25 21:42 ` Frank Li
2022-08-26 18:35 ` Marc Zyngier
2022-08-26 18:35 ` Marc Zyngier
2022-08-26 18:59 ` Frank Li
2022-08-26 18:59 ` Frank Li
2022-08-26 21:44 ` Marc Zyngier [this message]
2022-08-26 21:44 ` Marc Zyngier
2022-08-29 14:47 ` Frank Li
2022-08-29 14:47 ` Frank Li
2022-09-01 14:39 ` Frank Li
2022-09-01 14:39 ` Frank Li
2022-09-02 16:35 ` Rob Herring
2022-09-02 16:35 ` Rob Herring
2022-08-22 15:51 ` [PATCH v7 4/4] PCI: endpoint: Add NTB MSI support Frank Li
2022-08-22 15:51 ` Frank Li
2022-08-22 21:32 ` kernel test robot
2022-08-22 21:32 ` kernel test robot
2022-08-23 0:45 ` kernel test robot
2022-08-23 0:45 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgfqvfvv.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=jdmason@kudzu.us \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lznuaa@gmail.com \
--cc=ntb@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.