From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sm8650: Use GIC-ITS for PCIe0 and PCIe1
Date: Thu, 1 Feb 2024 20:59:22 +0100 [thread overview]
Message-ID: <0cf69024-a3e6-4be2-89ce-017ae521721d@linaro.org> (raw)
In-Reply-To: <20240125-topic-sm8650-upstream-pcie-its-v1-1-cb506deeb43e@linaro.org>
On 25.01.2024 17:55, Neil Armstrong wrote:
> Both PCIe0 and PCIe1 controllers are capable of signalling the MSIs
> received from endpoint devices to the CPU using GIC-ITS MSI controller.
> Add support for it.
>
> The GIC-ITS MSI implementation provides an advantage over internal MSI
> implementation using Locality-specific Peripheral Interrupts (LPI) that
> would allow MSIs to be targeted for each CPU core.
>
> Like SM8450 & SM8550, the IDs are swapped, but works fine on PCIe0 and PCIe1.
>
> WiFi PCIe Device on SM8650-QRD using GIC-ITS:
> 159: 0 0 0 0 0 0 0 0 ITS-MSI 0 Edge PCIe PME, aerdrv
> 167: 0 4 0 0 0 0 0 0 ITS-MSI 524288 Edge bhi
> 168: 0 0 4 0 0 0 0 0 ITS-MSI 524289 Edge mhi
> 169: 0 0 0 34 0 0 0 0 ITS-MSI 524290 Edge mhi
> 170: 0 0 0 0 3 0 0 0 ITS-MSI 524291 Edge ce0
> 171: 0 0 0 0 0 2 0 0 ITS-MSI 524292 Edge ce1
> 172: 0 0 0 0 0 0 806 0 ITS-MSI 524293 Edge ce2
> 173: 0 0 0 0 0 0 0 76 ITS-MSI 524294 Edge ce3
> 174: 0 0 0 0 0 0 0 0 ITS-MSI 524295 Edge ce5
> 175: 0 13 0 0 0 0 0 0 ITS-MSI 524296 Edge DP_EXT_IRQ
> 176: 0 0 0 0 0 0 0 0 ITS-MSI 524297 Edge DP_EXT_IRQ
Is it by chance that this one never fired?
(lgtm otherwise)
Konrad
next prev parent reply other threads:[~2024-02-01 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 16:55 Neil Armstrong
2024-02-01 19:59 ` Konrad Dybcio [this message]
2024-02-02 8:03 ` Neil Armstrong
2024-02-02 12:24 ` Konrad Dybcio
2024-02-03 17:06 ` Bjorn Andersson
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=0cf69024-a3e6-4be2-89ce-017ae521721d@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@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®