From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Chukun Pan" <amadeus@jmu.edu.cn>, "Heiko Stuebner" <heiko@sntech.de>
Cc: "Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Dragan Simic" <dsimic@manjaro.org>,
"Rob Herring" <robh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 0/1] arm64: dts: rockchip: rk3568: Move PCIe3 MSI to use GIC ITS
Date: Fri, 09 May 2025 17:34:21 +0200 [thread overview]
Message-ID: <D9RQN76VZXO8.T3I0046FNVG3@cknow.org> (raw)
In-Reply-To: <20250308093008.568437-1-amadeus@jmu.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
Hi,
On Sat Mar 8, 2025 at 10:30 AM CET, Chukun Pan wrote:
> For a long time, rk3568's MSI-X had bugs and could only work on one node.
> e.g. [ 7.250882] r8125 0002:01:00.0: no MSI/MSI-X. Back to INTx.
>
> Now the ITS of GICv3 on rk3568 has been fixed by commit b08e2f42e86b
> ("irqchip/gic-v3-its: Share ITS tables with a non-trusted hypervisor")
> and commit 2d81e1bb6252 ("irqchip/gic-v3: Add Rockchip 3568002 erratum
> workaround").
>
> Following commit b956c9de9175 ("arm64: dts: rockchip: rk356x: Move
> PCIe MSI to use GIC ITS instead of MBI"), change the PCIe3 controller's
> MSI on rk3568 to use ITS, so that all MSI-X can work properly.
>
> ~# dmesg | grep -E 'GIC|ITS'
> <snip>
>
> ~# lspci -v | grep MSI-X
> Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
> Capabilities: [b0] MSI-X: Enable- Count=128 Masked-
> Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
> Capabilities: [b0] MSI-X: Enable- Count=128 Masked-
> Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
I tested this patch on my NanoPi R5S with a 6.15-rc3 kernel + a number
of [vcc|phy]-supply patches that have been accepted for 6.16 (and a
small WIP LED patch).
With this patch I get the following kernel warnings:
pci 0001:10:00.0: Primary bus is hard wired to 0
pci 0002:20:00.0: Primary bus is hard wired to 0
If I 'unapply' this patch, I don't see those warnings.
The output of the above mentioned ``dmesg`` and ``lspci`` commands is
exactly the same in both cases.
The PCI IDs refer to:
PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
It's possible that this patch only brought a(nother) problem to light,
but was I supposed to see an improvement and if so where/how?
Cheers,
Diederik
> Chukun Pan (1):
> arm64: dts: rockchip: rk3568: Move PCIe3 MSI to use GIC ITS
>
> arch/arm64/boot/dts/rockchip/rk3568.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-09 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 9:30 [PATCH 0/1] arm64: dts: rockchip: rk3568: Move PCIe3 MSI to use GIC ITS Chukun Pan
2025-03-08 9:30 ` [PATCH 1/1] " Chukun Pan
2025-03-22 4:25 ` kernel test robot
2025-05-08 8:02 ` Chukun Pan
2025-05-08 18:30 ` Heiko Stuebner
2025-05-09 15:34 ` Diederik de Haas [this message]
2025-05-09 16:51 ` [PATCH 0/1] " Diederik de Haas
2025-05-12 7:00 ` Chukun Pan
2025-05-12 10:58 ` Diederik de Haas
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=D9RQN76VZXO8.T3I0046FNVG3@cknow.org \
--to=didi.debian@cknow.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).