From: Lucas Tanure <lucas.tanure@collabora.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Peter Geis <pgwipeout@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lucas Tanure <lucas.tanure@collabora.com>,
kernel@collabora.com
Subject: [RFC 0/1] ITS fails to allocate on rk3588
Date: Mon, 27 Feb 2023 15:18:46 +0000 [thread overview]
Message-ID: <20230227151847.207922-1-lucas.tanure@collabora.com> (raw)
I am assisting with PCIe and networking bring-up for Rock Pi 5B (RK3588).
This chip uses the same GICv3 as RK356X but has fixed the previous
limitation of GIC only supporting 32-bit addresses.
But the implementation decision for shareability in GICR and GITS is
still the same.
I read the previous thread about this topic:
https://lore.kernel.org/lkml/2791594e-db60-e1d0-88e5-7e5bbd98ae4d@rock-chips.com/T/#m5dbc70ff308d81e98dd0d797e23d3fbf9c353245
From my understanding, the errata numbers Marc Zyngier is referring to
are found in Arm errata documents at developer.arm.com/documentation.
But I could not find Cavium or Broadcom pages for errata with those
numbers in Documentation/arm64/silicon-errata.rst
I could not find an errata document about this shareability issue,
and by what Kever said in the previous thread this could be a
RockChip design decision.
Marc, as I could only find ARM errata numbers, is the errata number
you were expecting generated by ARM only, or RockChip should issue
a document like Arm to detail the issue?
Can this shareability issue be seen as a quirk without an
errata number?
The following patch is based on the work of Peter Geis for the
Quartz64 board and the previous thread feedback.
Lucas Tanure (1):
irqchip/gic-v3: Add RK3588 GICR and GITS no share workaround
Documentation/arm64/silicon-errata.rst | 4 +++
arch/arm64/Kconfig | 13 ++++++++
drivers/irqchip/irq-gic-v3-its.c | 42 ++++++++++++++++++++++++++
3 files changed, 59 insertions(+)
--
2.39.2
next reply other threads:[~2023-02-27 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 15:18 Lucas Tanure [this message]
2023-02-27 15:18 ` [RFC 1/1] irqchip/gic-v3: Add RK3588 GICR and GITS no share workaround Lucas Tanure
2023-02-28 8:35 ` AngeloGioacchino Del Regno
2023-02-28 17:21 ` Robin Murphy
2023-02-27 21:22 ` [RFC 0/1] ITS fails to allocate on rk3588 Peter Geis
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=20230227151847.207922-1-lucas.tanure@collabora.com \
--to=lucas.tanure@collabora.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maz@kernel.org \
--cc=pgwipeout@gmail.com \
--cc=tglx@linutronix.de \
--cc=will@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).