Home
last modified time | relevance | path

Searched full:gics (Results 1 – 9 of 9) sorted by relevance

/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Darm,gic.yaml18 Secondary GICs are cascaded into the upward interrupt controller and do not
113 secondary GICs, or VGIC maintenance interrupt on primary GIC (see
/openbmc/qemu/hw/intc/
H A Drealview_gic.c29 /* The GICs on the RealView boards have a fixed nonconfigurable in realview_gic_realize()
H A Darm_gic_common.c305 /* For uniprocessor GICs all interrupts always target the sole CPU */ in arm_gic_common_reset_hold()
H A Darm_gic.c1081 /* For uniprocessor GICs these RAZ/WI */ in gic_dist_readb()
1217 * GIC, or for GICs without groups. in gic_dist_writeb()
1404 /* Interrupt CPU Target. RAZ/WI on uniprocessor GICs, with the in gic_dist_writeb()
/openbmc/linux/include/linux/irqchip/
H A Darm-gic.h144 * chips and call this to register their GICs.
/openbmc/linux/drivers/perf/
H A Darm_pmu_acpi.c48 * "performance interrupt". Luckily, on compliant GICs the polarity is in arm_pmu_acpi_register_irq()
/openbmc/linux/Documentation/arch/arm64/
H A Dacpi_object_usage.rst700 MADT for GICs are expected to be in synchronization. The _UID of the Device
769 - Section 9.17: I/O APIC devices; all GICs must be enumerable via MADT
/openbmc/linux/arch/arm64/kvm/vgic/
H A Dvgic-init.c580 * If we get one of these oddball non-GICs, taint the kernel, in kvm_vgic_hyp_init()
/openbmc/linux/drivers/irqchip/
H A Dirq-gic.c499 * because any nested/secondary GICs do not directly interface in gic_cpu_init()