Searched full:gicv5 (Results 1 – 13 of 13) sorted by relevance
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | arm,gic-v5-iwb.yaml | 14 The GICv5 architecture defines the guidelines to implement GICv5 17 The GICv5 specification can be found at 20 GICv5 has zero or more Interrupt Wire Bridges (IWB) that are responsible 21 for translating wire signals into interrupt messages to the GICv5 ITS.
|
H A D | arm,gic-v5.yaml | 14 The GICv5 architecture defines the guidelines to implement GICv5 17 The GICv5 specification can be found at 20 The GICv5 architecture is composed of multiple components: 81 GICv5 has one or more Interrupt Routing Services (IRS) that are 135 GICv5 has zero or more Interrupt Translation Services (ITS) that are 176 GICv5 ITS has one or more translate register frames.
|
/linux/drivers/irqchip/ |
H A D | irq-gic-v5-iwb.c | 5 #define pr_fmt(fmt) "GICv5 IWB: " fmt 159 .name = "GICv5-IWB", 270 .name = "GICv5 IWB",
|
H A D | irq-gic-v5-irs.c | 6 #define pr_fmt(fmt) "GICv5 IRS: " fmt 73 /* Taken from GICv5 specifications 10.2.1.13 IRS_IST_BASER */ in gicv5_irs_init_ist_linear() 137 /* Taken from GICv5 specifications 10.2.1.13 IRS_IST_BASER */ in gicv5_irs_init_ist_two_level() 349 * Follow GICv5 specification recommendation to opt in for two in gicv5_irs_init_ist() 703 pr_err("%pOF: unable to map GICv5 IRS registers\n", node); in gicv5_irs_init()
|
H A D | irq-gic-v5-its.c | 6 #define pr_fmt(fmt) "GICv5 ITS: " fmt 579 * We expect a GICv5 implementation requiring a large number of in gicv5_its_alloc_devtab_linear() 725 .name = "GICv5-ITS-MSI", 1206 pr_err("%pOF: unable to map GICv5 ITS_CONFIG_FRAME\n", node); in gicv5_its_init()
|
H A D | irq-gic-its-msi-parent.c | 195 * in GICv5 (where the msi controller nodes are the in of_v5_pmsi_get_msi_info()
|
/linux/include/kvm/ |
H A D | arm_vgic.h | 41 VGIC_V5, /* Newer, fancier GICv5 */ 84 /* GICv3 compat mode on a GICv5 host */
|
/linux/Documentation/arch/arm64/ |
H A D | booting.rst | 226 For systems with a GICv5 interrupt controller to be used in v5 mode: 265 - The DT or ACPI tables must describe a GICv5 interrupt controller.
|
/linux/arch/arm64/include/asm/ |
H A D | el2_setup.h | 201 /* GICv5 system register access */
|
/linux/Documentation/virt/kvm/devices/ |
H A D | arm-vgic-v3.rst | 16 Creating a guest GICv3 device requires a host GICv3 host, or a GICv5 host with
|
/linux/arch/arm64/kernel/ |
H A D | cpufeature.c | 3079 .desc = "GICv5 CPU interface", 3086 .desc = "GICv5 Legacy vCPU interface",
|
/linux/arch/arm64/kvm/ |
H A D | arm.c | 2334 kvm_err("NV support requires GICv3 or GICv5 with legacy support, giving up\n"); in init_subsystems()
|
H A D | sys_regs.c | 2163 * If we are running on a GICv5 host and support FEAT_GCIE_LEGACY, then in set_id_aa64pfr0_el1()
|