From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Olof Johansson" <olof@lixom.net>,
"Masami Hiramatsu" <mhiramat@kernel.org>
Cc: soc@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: uniphier: Add NX1 SoC and boards support
Date: Thu, 27 Oct 2022 13:28:28 +0200 [thread overview]
Message-ID: <dcbbde62-fcf1-4435-8f65-665b25ec3b0a@app.fastmail.com> (raw)
In-Reply-To: <8c11d7c4-dfc4-b84c-82cd-a9708bd79aab@socionext.com>
On Thu, Oct 27, 2022, at 13:19, Kunihiko Hayashi wrote:
> On 2022/10/27 19:01, Arnd Bergmann wrote:
>> On Thu, Oct 27, 2022, at 06:51, Kunihiko Hayashi wrote:
>>> + #interrupt-cells = <1>;
>>> + interrupt-names = "dma", "msi";
>>> + interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>,
>>> + <GIC_SPI 85 IRQ_TYPE_LEVEL_HIGH>;
>>> + interrupt-map-mask = <0 0 0 7>;
>>> + interrupt-map = <0 0 0 1 &pcie_intc 0>, /* INTA */
>>> + <0 0 0 2 &pcie_intc 1>, /* INTB */
>>> + <0 0 0 3 &pcie_intc 2>, /* INTC */
>>> + <0 0 0 4 &pcie_intc 3>; /* INTD */
>>> + phy-names = "pcie-phy";
>>> + phys = <&pcie_phy>;
>>> +
>>> + pcie_intc: legacy-interrupt-controller {
>>> + interrupt-controller;
>>> + #interrupt-cells = <1>;
>>> + interrupt-parent = <&gic>;
>>> + interrupts = <GIC_SPI 86
>> IRQ_TYPE_LEVEL_HIGH>;
>>> + };
>>> + };
>>
>> Shouldn't there be an "msi-map" or "msi-parent" property pointing at
>> the GIC?
>
> Since Designware PCIe receives an interrupt from GIC with interrupt-name "msi"
> and passes the interrupt to the linear irq domain corresponding to MSI,
> I think there is neither "msi-map" nor "msi-parent" properties.
Usually, you have the choice to use either the built-in
MSI logic of the PCIe controller, or the one built into the
GIC itself, assuming you have a modern enough GIC implemetation.
Using the GIC is preferred here, because otherwise you lose
all the benefits that MSIs offer, regarding latency and CPU
affinity.
Arnd
next prev parent reply other threads:[~2022-10-27 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:51 [PATCH 0/4] Add UniPhier " Kunihiko Hayashi
2022-10-27 4:51 ` [PATCH 1/4] dt-bindings: arm: uniphier: Add Pro5 boards Kunihiko Hayashi
2022-10-27 13:28 ` Krzysztof Kozlowski
2022-10-27 4:51 ` [PATCH 2/4] ARM: dts: uniphier: Add Pro5 board support Kunihiko Hayashi
2022-10-27 4:51 ` [PATCH 3/4] dt-bindings: arm: uniphier: Add NX1 boards Kunihiko Hayashi
2022-10-27 13:29 ` Krzysztof Kozlowski
2022-10-27 4:51 ` [PATCH 4/4] arm64: dts: uniphier: Add NX1 SoC and boards support Kunihiko Hayashi
2022-10-27 10:01 ` Arnd Bergmann
2022-10-27 11:19 ` Kunihiko Hayashi
2022-10-27 11:28 ` Arnd Bergmann [this message]
2022-10-27 11:58 ` Kunihiko Hayashi
2022-10-27 12:19 ` Arnd Bergmann
2022-10-27 13:36 ` Krzysztof Kozlowski
2022-11-01 9:02 ` Kunihiko Hayashi
2022-11-02 16:48 ` Krzysztof Kozlowski
2022-11-04 5:57 ` Kunihiko Hayashi
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=dcbbde62-fcf1-4435-8f65-665b25ec3b0a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®