From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] implement workaround for Socionext Synquacer pre-ITS
Date: Thu, 12 Oct 2017 19:32:45 +0100 [thread overview]
Message-ID: <20171012183247.23679-1-ard.biesheuvel@linaro.org> (raw)
>From patch 2/2:
The Socionext Synquacer SoC's implementation of GICv3 has a so-called
'pre-ITS', which maps 32-bit writes targeted at a separate window of
size '4 << device_id_bits' onto writes to GITS_TRANSLATER with device
ID taken from bits [device_id_bits + 1:2] of the window offset.
Writes that target GITS_TRANSLATER directly are reported as originating
from device ID #0.
So add a workaround for this. Given that this breaks isolation, clear
the IRQ_DOMAIN_FLAG_MSI_REMAP flag as well.
v3: - add patch to pull device ID space discovery forward, so we can quirk
it as well (as we already do for Cavium)
- use existing quirks framework as much as possible
- get rid of ITS_WORKAROUND_xxx flag: it is no longer needed after the
refactoring
v2: - use a 32-bit host address/size rather than a PCI address, to factor
out the involvement of an SMMU (which the platform does have, but it
is unclear atm if it can be exposed to the OS)
- add msi_domain_flags member to move the quirk flag checks out of the
common code path
Ard Biesheuvel (2):
drivers/irqchip: gicv3: probe device ID space before quirks handling
drivers/irqchip: gicv3: add workaround for Synquacer pre-ITS
Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 4 +
arch/arm64/Kconfig | 8 ++
drivers/irqchip/irq-gic-v3-its.c | 81 ++++++++++++++++----
3 files changed, 78 insertions(+), 15 deletions(-)
--
2.11.0
next reply other threads:[~2017-10-12 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 18:32 Ard Biesheuvel [this message]
2017-10-12 18:32 ` [PATCH v3 1/2] drivers/irqchip: gicv3: probe device ID space before quirks handling Ard Biesheuvel
2017-10-12 18:32 ` [PATCH v3 2/2] drivers/irqchip: gicv3: add workaround for Synquacer pre-ITS Ard Biesheuvel
2017-10-12 19:11 ` Ard Biesheuvel
2017-10-13 10:00 ` Marc Zyngier
2017-10-12 21:34 ` Rob Herring
2017-10-12 22:24 ` Ard Biesheuvel
2017-10-13 9:47 ` Marc Zyngier
2017-10-13 9:55 ` Ard Biesheuvel
2017-10-13 10:02 ` Marc Zyngier
2017-10-13 18:50 ` Rob Herring
2017-10-13 20:38 ` Ard Biesheuvel
2017-10-14 9:13 ` Marc Zyngier
2017-10-14 9:05 ` Marc Zyngier
2017-10-17 17:31 ` Rob Herring
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=20171012183247.23679-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).