From: Marc Zyngier <maz@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>, Peng Fan <peng.fan@nxp.com>,
Robin Murphy <robin.murphy@arm.com>,
Peter Geis <pgwipeout@gmail.com>,
XiaoDong Huang <derrick.huang@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: rk3588: add MSI support
Date: Mon, 17 Apr 2023 17:39:10 +0100 [thread overview]
Message-ID: <868reqlaz5.wl-maz@kernel.org> (raw)
In-Reply-To: <20230417150038.51698-3-sebastian.reichel@collabora.com>
On Mon, 17 Apr 2023 16:00:38 +0100,
Sebastian Reichel <sebastian.reichel@collabora.com> wrote:
>
> Add the two Interrupt Translation Service (ITS) IPs that are part of the
> GIC-600, which are required for message signalled interrupts (MSI). This
> is required for PCIe, which fully relies on MSI for interrupts.
>
> Enabling the ITS nodes requires an operating system, that has a
> workaround for Rockchip errata #3588001 (GIC600 can not support
> shareable attribute).
$SUBJECT is inaccurate. This adds the descriptions of the ITSs, but
doesn't wire any MSI support at all (nobody even refers these
nodes, so the whole thing is pretty pointless).
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2023-04-17 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 15:00 [PATCH v2 0/2] Add Rockchip RK3588 GIC ITS support Sebastian Reichel
2023-04-17 15:00 ` [PATCH v2 1/2] irqchip/gic-v3: Add Rockchip 3588001 errata workaround Sebastian Reichel
2023-04-17 16:20 ` Marc Zyngier
2023-04-17 21:40 ` Sebastian Reichel
2023-04-18 8:58 ` Marc Zyngier
2023-04-18 14:34 ` Sebastian Reichel
2023-04-17 15:00 ` [PATCH v2 2/2] arm64: dts: rockchip: rk3588: add MSI support Sebastian Reichel
2023-04-17 16:39 ` Marc Zyngier [this message]
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=868reqlaz5.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=derrick.huang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastian.reichel@collabora.com \
--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 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).