mbox series

[0/6] irqchip/gic-v3: Disable pseudo NMIs on Mediatek Chromebooks w/ bad FW

Message ID 20230511150539.6.Ia0b6ebbaa351e3cd67e201355b9ae67783c7d718@changeid (mailing list archive)
Headers show
Series irqchip/gic-v3: Disable pseudo NMIs on Mediatek Chromebooks w/ bad FW | expand

Message

Doug Anderson May 11, 2023, 10:05 p.m. UTC
As talked about in the bindings patch included in this series
("dt-bindings: interrupt-controller: arm,gic-v3: Add quirk for
Mediatek SoCs w/ broken FW"), many Mediatek-based Chromebooks shipped
with firmware that doesn't properly save/restore some GICR
registers. This causes the system to crash if "pseudo NMIs" are turned
on.

This series makes sure that we never allow turning on "pseudo NMIs" if
we are running with the problematic firmware.

The patches in this series can land in any order and can go through
entirely different trees. None of the patches are harmful on their
own, but to get things fixed we need all of them.


Douglas Anderson (6):
  dt-bindings: interrupt-controller: arm,gic-v3: Add quirk for Mediatek
    SoCs w/ broken FW
  irqchip/gic-v3: Disable pseudo NMIs on Mediatek devices w/ firmware
    issues
  arm64: dts: mediatek: mt8183: Add mediatek,gicr-save-quirk
  arm64: dts: mediatek: mt8186: Add mediatek,gicr-save-quirk
  arm64: dts: mediatek: mt8192: Add mediatek,gicr-save-quirk
  arm64: dts: mediatek: mt8195: Add mediatek,gicr-save-quirk

 .../interrupt-controller/arm,gic-v3.yaml      |  6 ++++++
 arch/arm64/boot/dts/mediatek/mt8183.dtsi      |  1 +
 arch/arm64/boot/dts/mediatek/mt8186.dtsi      |  1 +
 arch/arm64/boot/dts/mediatek/mt8192.dtsi      |  1 +
 arch/arm64/boot/dts/mediatek/mt8195.dtsi      |  1 +
 drivers/irqchip/irq-gic-common.c              |  8 ++++++--
 drivers/irqchip/irq-gic-common.h              |  1 +
 drivers/irqchip/irq-gic-v3.c                  | 20 +++++++++++++++++++
 8 files changed, 37 insertions(+), 2 deletions(-)

Comments

Julius Werner May 11, 2023, 10:38 p.m. UTC | #1
Reviewed-by: Julius Werner <jwerner@chromium.org>
Julius Werner May 11, 2023, 10:38 p.m. UTC | #2
Reviewed-by: Julius Werner <jwerner@chromium.org>
Julius Werner May 11, 2023, 10:38 p.m. UTC | #3
Reviewed-by: Julius Werner <jwerner@chromium.org>