Home
last modified time | relevance | path

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

12

/kernel/linux/linux-4.19/drivers/perf/
Darm_pmu_acpi.c51 * a fixed value in HW (for both SPIs and PPIs) that we cannot change in arm_pmu_acpi_register_irq()
110 * corresponding GSI once (e.g. when we have PPIs). in arm_pmu_acpi_parse_irqs()
149 * the PMU (e.g. we don't have mismatched PPIs).
169 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()
/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-4.19/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic.txt7 Primary GIC is attached directly to the CPU and typically has PPIs and SGIs.
9 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.txt32 interrupt types other than PPI or PPIs that are not partitionned,
/kernel/linux/linux-5.10/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-4.19/drivers/acpi/arm64/
Dgtdt.c89 * acpi_gtdt_map_ppi() - Map the PPIs of per-cpu arch_timer.
93 * 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-4.19/Documentation/devicetree/bindings/timer/
Darm,arch_timer.txt8 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
/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-4.19/virt/kvm/arm/vgic/
Dvgic-init.c221 * configure all PPIs as level-triggered. in kvm_vgic_vcpu_init()
237 /* PPIs */ in kvm_vgic_vcpu_init()
Dvgic.c104 /* SGIs and PPIs */ in vgic_get_irq()
404 * @cpuid: The CPU for PPIs
560 * @vcpu: Pointer to the VCPU (used for PPIs)
/kernel/linux/linux-5.10/drivers/gpio/
Dgpio-xgene-sb.c195 /* Skip SGIs and PPIs*/ in xgene_gpio_sb_domain_alloc()
/kernel/linux/linux-5.10/include/kvm/
Darm_vgic.h97 struct kvm_vcpu *vcpu; /* SGIs and PPIs: The VCPU
/kernel/linux/linux-4.19/Documentation/virtual/kvm/devices/
Darm-vgic-v3.txt242 PPIs are reported per VCPU as specified in the mpidr field, and SPIs are
/kernel/linux/linux-4.19/include/kvm/
Darm_vgic.h107 struct kvm_vcpu *vcpu; /* SGIs and PPIs: The VCPU
/kernel/linux/linux-4.19/drivers/gpio/
Dgpio-xgene-sb.c206 /* Skip SGIs and PPIs*/ in xgene_gpio_sb_domain_alloc()

12