Home
last modified time | relevance | path

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

12

/linux-6.12.1/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()
Darm_spe_pmu.c1159 /* Request our PPIs (note that the IRQ is still disabled) */ in arm_spe_pmu_dev_init()
/linux-6.12.1/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 partitioned,
/linux-6.12.1/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-6.12.1/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
/linux-6.12.1/drivers/clocksource/
Dtimer-mediatek-cpux.c87 * on the CPU timer PPIs as well, so we don't declare TIMER_OF_IRQ.
/linux-6.12.1/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()
/linux-6.12.1/arch/arm64/kvm/vgic/
Dvgic.c90 /* SGIs and PPIs */ in vgic_get_irq()
410 * @vcpu: The CPU for PPIs or NULL for global interrupts
579 * @vcpu: Pointer to the VCPU (used for PPIs)
Dvgic-init.c202 * configure all PPIs as level-triggered. in vgic_allocate_private_irqs_locked()
218 /* PPIs */ in vgic_allocate_private_irqs_locked()
Dvgic-mmio.c746 * for PPIs this is IMPLEMENTATION DEFINED. The arch timer in vgic_mmio_write_config()
747 * code relies on PPIs being level triggered, so we also in vgic_mmio_write_config()
Dvgic-kvm-device.c228 * - at least 32 SPIs on top of the 16 SGIs and 16 PPIs in vgic_set_common_attr()
Dvgic-mmio-v3.c569 * The GICv3 per-IRQ registers are split to control PPIs and SGIs in the
/linux-6.12.1/drivers/gpio/
Dgpio-xgene-sb.c194 /* Skip SGIs and PPIs*/ in xgene_gpio_sb_domain_alloc()
/linux-6.12.1/tools/testing/selftests/kvm/lib/aarch64/
Dgic_v3.c317 /* Set a default priority for all the SGIs and PPIs */ in gicv3_cpu_init()
/linux-6.12.1/drivers/irqchip/
Dirq-hip04.c135 /* Misconfigured PPIs are usually not fatal */ in hip04_irq_set_type()
Dirq-gic-v3.c754 /* Misconfigured PPIs are usually not fatal */ in gic_set_type()
1152 pr_info("GICv3 features: %d PPIs%s%s\n", in gic_update_rdist_properties()
1317 /* Configure SGIs/PPIs as non-secure Group-1 */ in gic_cpu_init()
1660 * Partitioned PPIs are an unfortunate exception. in gic_irq_domain_translate()
/linux-6.12.1/tools/testing/selftests/kvm/aarch64/
Dvgic_irq.c97 /* can inject PPIs, PPIs, and/or SPIs. */
/linux-6.12.1/include/kvm/
Darm_vgic.h123 struct kvm_vcpu *vcpu; /* SGIs and PPIs: The VCPU
/linux-6.12.1/Documentation/virt/kvm/devices/
Darm-vgic-v3.rst284 PPIs are reported per VCPU as specified in the mpidr field, and SPIs are
/linux-6.12.1/drivers/net/hyperv/
Dhyperv_net.h939 u8 ppi_flags; /* valid/present bits for the above PPIs */
Drndis_filter.c410 /* Copy the PPIs into nvchan->recv_buf */ in rndis_get_ppi()

12