diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2017-10-27 11:34:22 +0300 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2017-11-02 18:55:44 +0300 |
commit | 0962289b1cd91534f7111e763d3e6a17dcd47ecb (patch) | |
tree | 4632cbba7bdd33596de6e94c77f2ed0997834e24 /include/linux/irqdomain.h | |
parent | d4d7b4ad2f05c03fb25252aea66f9f3cd7cfbe06 (diff) | |
download | linux-0962289b1cd91534f7111e763d3e6a17dcd47ecb.tar.xz |
irqchip/gic: Deal with broken firmware exposing only 4kB of GICv2 CPU interface
There is a lot of broken firmware out there that don't really
expose the information the kernel requires when it comes with dealing
with GICv2:
(1) Firmware that only describes the first 4kB of GICv2
(2) Firmware that describe 128kB of CPU interface, while
the usable portion of the address space is between
60 and 68kB
So far, we only deal with (2). But we have platforms exhibiting
behaviour (1), resulting in two sub-cases:
(a) The GIC is occupying 8kB, as required by the GICv2 architecture
(b) It is actually spread 128kB, and this is likely to be a version
of (2)
This patch tries to work around both (a) and (b) by poking at
the outside of the described memory region, and try to work out
what is actually there. This is of course unsafe, and should
only be enabled if there is no way to otherwise fix the DT provided
by the firmware (we provide a "irqchip.gicv2_force_probe" option
to that effect).
Note that for the time being, we restrict ourselves to GICv2
implementations provided by ARM, since there I have no knowledge
of an alternative implementations. This could be relaxed if such
an implementation comes to light on a broken platform.
Reviewed-by: Christoffer Dall <cdall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'include/linux/irqdomain.h')
0 files changed, 0 insertions, 0 deletions