diff options
| author | Marc Zyngier <maz@kernel.org> | 2026-07-25 16:59:41 +0100 |
|---|---|---|
| committer | Thomas Gleixner <tglx@kernel.org> | 2026-09-04 15:34:33 +0200 |
| commit | b36bfa477b77901a247e7a192e7404b39e9f522d (patch) | |
| tree | 018c99f974c6de88eab8d19590998082f42b5a50 /scripts/Makefile.thinlto | |
| parent | bd7d57a03c4b0fa3b0291ec64d688ebfed5edffc (diff) | |
| download | linux-next-b36bfa477b77901a247e7a192e7404b39e9f522d.tar.gz linux-next-b36bfa477b77901a247e7a192e7404b39e9f522d.zip | |
irqchip/gic: Simplify Maintenance Interrupt ACPI parsing
The ACPI spec describes the vgic Maintenance Interrupt with attributes
indicating whether the signalling is Level or Edge. While this
superficially looks like a sensible thing to do, it doesn't actually
make much sense.
By construction, this interrupt is Level, and cannot be anything
else, as the hypervisor actively needs to interact with the vgic
for the level to drop. This indicates a state, and not an event.
Get rid of this nonsense, always register the corresponding GSI as
Level, and let the user know that they run on quality FW should
the interrupt be advertised as Edge.
Signed-off-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Reviewed-by: Zenghui Yu <yuzenghui@huawei.com>
Reviewed-by: Radu Rendec <radu@rendec.net>
Link: https://patch.msgid.link/20260725155941.114322-1-maz@kernel.org
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
