Home
last modified time | relevance | path

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

12

/kernel/linux/linux-5.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.c137 pr_warn("multiple PPIs or mismatched SPI/PPI detected\n"); in pmu_parse_irqs()
/kernel/linux/linux-6.6/drivers/perf/
Darm_pmu_acpi.c49 * a fixed value in HW (for both SPIs and PPIs) that we cannot change in arm_pmu_acpi_register_irq()
238 * corresponding GSI once (e.g. when we have PPIs). in arm_pmu_acpi_parse_irqs()
268 * the PMU (e.g. we don't have mismatched PPIs).
288 pr_warn("mismatched PPIs detected\n"); in pmu_irq_matches()
Darm_pmu_platform.c134 dev_warn(dev, "multiple PPIs or mismatched SPI/PPI detected\n"); in pmu_parse_irqs()
/kernel/linux/linux-5.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,
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/
Dti,omap4-wugen-mpu20 - Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
Darm,gic.yaml17 Primary GIC is attached directly to the CPU and typically has PPIs and SGIs.
19 have PPIs or SGIs.
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,
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
/kernel/linux/linux-6.6/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,
/kernel/linux/linux-5.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,
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
/kernel/linux/linux-6.6/drivers/clocksource/
Dtimer-mediatek-cpux.c87 * on the CPU timer PPIs as well, so we don't declare TIMER_OF_IRQ.
/kernel/linux/linux-5.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()
424 * @cpuid: The CPU for PPIs
580 * @vcpu: Pointer to the VCPU (used for PPIs)
/kernel/linux/linux-6.6/arch/arm64/kvm/vgic/
Dvgic-init.c209 * configure all PPIs as level-triggered. in kvm_vgic_vcpu_init()
225 /* PPIs */ in kvm_vgic_vcpu_init()
Dvgic.c95 /* SGIs and PPIs */ in vgic_get_irq()
425 * @cpuid: The CPU for PPIs
596 * @vcpu: Pointer to the VCPU (used for PPIs)
/kernel/linux/linux-6.6/arch/arm64/kvm/
Darch_timer.c1454 u32 ppis = 0; in timer_irqs_are_valid() local
1469 * We know by construction that we only have PPIs, so in timer_irqs_are_valid()
1472 ppis |= BIT(irq); in timer_irqs_are_valid()
1475 valid = hweight32(ppis) == nr_timers(vcpu); in timer_irqs_are_valid()
/kernel/linux/linux-6.6/drivers/gpio/
Dgpio-xgene-sb.c195 /* Skip SGIs and PPIs*/ in xgene_gpio_sb_domain_alloc()
/kernel/linux/linux-5.10/drivers/gpio/
Dgpio-xgene-sb.c195 /* Skip SGIs and PPIs*/ in xgene_gpio_sb_domain_alloc()
/kernel/linux/linux-6.6/tools/testing/selftests/kvm/lib/aarch64/
Dgic_v3.c308 /* Set a default priority for all the SGIs and PPIs */ in gicv3_cpu_init()

12