Home
last modified time | relevance | path

Searched full:ppis (Results 1 – 21 of 21) sorted by relevance

/Linux-v5.10/drivers/perf/
Darm_pmu_acpi.c48 * a fixed value in HW (for both SPIs and PPIs) that we cannot change in arm_pmu_acpi_register_irq()
177 * corresponding GSI once (e.g. when we have PPIs). in arm_pmu_acpi_parse_irqs()
216 * the PMU (e.g. we don't have mismatched PPIs).
236 pr_warn("mismatched PPIs detected\n"); in pmu_irq_matches()
Darm_pmu_platform.c138 pr_warn("multiple PPIs or mismatched SPI/PPI detected\n"); in pmu_parse_irqs()
Darm_spe_pmu.c1105 /* Request our PPIs (note that the IRQ is still disabled) */ in arm_spe_pmu_dev_init()
/Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic.yaml17 Primary GIC is attached directly to the CPU and typically has PPIs and SGIs.
19 have PPIs or SGIs.
Dti,omap4-wugen-mpu20 - Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
Dnvidia,tegra20-ictlr.txt27 - Only SPIs can use the ictlr as an interrupt parent. SGIs and PPIs
Darm,gic-v3.yaml63 interrupt types other than PPI or PPIs that are not partitionned,
/Linux-v5.10/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
/Linux-v5.10/drivers/acpi/arm64/
Dgtdt.c86 * acpi_gtdt_map_ppi() - Map the PPIs of per-cpu arch_timer.
90 * So we only handle the non-secure timer PPIs,
/Linux-v5.10/arch/arm64/kvm/vgic/
Dvgic-init.c200 * configure all PPIs as level-triggered. in kvm_vgic_vcpu_init()
216 /* PPIs */ in kvm_vgic_vcpu_init()
Dvgic.c93 /* SGIs and PPIs */ in vgic_get_irq()
423 * @cpuid: The CPU for PPIs
579 * @vcpu: Pointer to the VCPU (used for PPIs)
Dvgic-mmio.c724 * for PPIs this is IMPLEMENTATION DEFINED. The arch timer in vgic_mmio_write_config()
725 * code relies on PPIs being level triggered, so we also in vgic_mmio_write_config()
Dvgic-kvm-device.c182 * - at least 32 SPIs on top of the 16 SGIs and 16 PPIs in vgic_set_common_attr()
Dvgic-mmio-v3.c522 * The GICv3 per-IRQ registers are split to control PPIs and SGIs in the
/Linux-v5.10/drivers/gpio/
Dgpio-xgene-sb.c195 /* Skip SGIs and PPIs*/ in xgene_gpio_sb_domain_alloc()
/Linux-v5.10/include/kvm/
Darm_vgic.h97 struct kvm_vcpu *vcpu; /* SGIs and PPIs: The VCPU
/Linux-v5.10/drivers/irqchip/
Dirq-gic-v3.c579 /* Misconfigured PPIs are usually not fatal */ in gic_set_type()
889 pr_info("%d PPIs implemented\n", gic_data.ppi_nr); in gic_update_rdist_properties()
1056 /* Configure SGIs/PPIs as non-secure Group-1 */ in gic_cpu_init()
1388 * Partitionned PPIs are an unfortunate exception. in gic_irq_domain_translate()
Dirq-hip04.c135 /* Misconfigured PPIs are usually not fatal */ in hip04_irq_set_type()
Dirq-gic.c308 /* Misconfigured PPIs are usually not fatal */ in gic_set_type()
/Linux-v5.10/Documentation/virt/kvm/devices/
Darm-vgic-v3.rst277 PPIs are reported per VCPU as specified in the mpidr field, and SPIs are
/Linux-v5.10/Documentation/virt/kvm/
Dapi.rst831 use PPIs designated for specific cpus. The irq field is interpreted