Home
last modified time | relevance | path

Searched full:gicv2 (Results 1 – 25 of 62) sorted by relevance

123

/OK3568_Linux_fs/kernel/include/kvm/
H A Darm_vgic.h37 VGIC_V2, /* Good ol' GICv2 */
65 /* maximum number of VCPUs allowed (GICv2 limits us to 8) */
120 u8 targets; /* GICv2 target VCPUs mask */
123 u8 source; /* GICv2 SGIs only */
124 u8 active_source; /* GICv2 SGIs only */
208 /* vGIC model the kernel emulates for the guest (GICv2 or GICv3) */
214 /* Userspace can write to GICv2 IGROUPR */
225 /* either a GICv2 CPU interface */
/OK3568_Linux_fs/kernel/Documentation/virt/kvm/devices/
H A Darm-vgic.rst17 guest GICv2 through this interface. For information on creating a guest GICv3
19 create both a GICv3 and GICv2 device on the same VM.
58 GICv2 specs. Getting or setting such a register has the same effect as
65 GICv2 is changed in a way directly observable by the guest or userspace.
92 defined in the GICv2 specs. Getting or setting such a register has the
96 fixed format for our implementation that fits with the model of a "GICv2
112 similar to GICv2's GICH_APR.
/OK3568_Linux_fs/u-boot/arch/arm/mach-rockchip/
H A DKconfig6 select GICV2
63 select GICV2
139 select GICV2
168 select GICV2
214 imply GICV2
249 select GICV2
293 select GICV2
387 select GICV2 if !ARM64_BOOT_AARCH32
413 select GICV2
588 imply GICV2
[all …]
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/arm/
H A Dfoundation-v8-psci.dts4 * ARMv8 Foundation model DTS (GICv2+PSCI configuration)
8 #include "foundation-v8-gicv2.dtsi"
H A Dfoundation-v8.dts5 * ARMv8 Foundation model DTS (GICv2 configuration)
9 #include "foundation-v8-gicv2.dtsi"
H A Dfoundation-v8-gicv2.dtsi4 * ARMv8 Foundation model DTS (GICv2 configuration)
/OK3568_Linux_fs/buildroot/boot/boot-wrapper-aarch64/
H A DConfig.in42 bool "Enable GICv3 instead of GICv2"
44 Boot using GICv3 instead of GICv2.
/OK3568_Linux_fs/kernel/arch/arm64/kvm/vgic/
H A Dvgic-mmio-v2.c20 * Revision 1: Report GICv2 interrupts as group 0 instead of group 1
359 /* GICv2 hardware systems support max. 32 groups */ in vgic_mmio_read_apr()
371 /* GICv3 only uses ICH_AP1Rn for memory mapped (GICv2) guests */ in vgic_mmio_read_apr()
385 /* GICv2 hardware systems support max. 32 groups */ in vgic_mmio_write_apr()
397 /* GICv3 only uses ICH_AP1Rn for memory mapped (GICv2) guests */ in vgic_mmio_write_apr()
H A Dvgic-init.c33 * structures. Can be executed lazily for GICv2.
81 * which had no chance yet to check the availability of the GICv2 in kvm_vgic_create()
147 * initialization when using a virtual GICv2. in kvm_vgic_dist_init()
390 * is a GICv2. A GICv3 must be explicitly initialized by the guest using the
401 * for the legacy case of a GICv2. Any other type must in vgic_lazy_init()
H A Dvgic-v3.c283 * If we are emulating a GICv3, we do it in an non-GICv2-compatible in vgic_v3_enable()
615 kvm_err("Cannot register GICv2 KVM device.\n"); in vgic_v3_probe()
628 kvm_info("disabling GICv2 emulation\n"); in vgic_v3_probe()
655 * If dealing with a GICv2 emulation on GICv3, VMCR_EL2.VFIQen in vgic_v3_load()
H A Dvgic-mmio.c342 * GICv2 SGIs are terribly broken. We can't restore in vgic_uaccess_write_spending()
434 * More fun with GICv2 SGIs! If we're clearing one of them in vgic_uaccess_write_cpending()
461 * For GICv2 private interrupts we don't have to do anything because
563 * The GICv2 architecture indicates that the source CPUID for in vgic_mmio_change_active()
571 * for a GICv2 VM on some GIC implementations. Oh well. in vgic_mmio_change_active()
H A Dvgic-v2.c209 /* The GICv2 LR only holds five bits of priority. */ in vgic_v2_populate_lr()
398 kvm_err("Cannot register GICv2 KVM device\n"); in vgic_v2_probe()
H A Dvgic-debug.c149 seq_printf(s, "vgic_model:\t%s\n", v3 ? "GICv3" : "GICv2"); in print_dist_state()
H A Dvgic.h132 * state to userspace can generate either GICv2 or GICv3 CPU interface
/OK3568_Linux_fs/kernel/drivers/irqchip/
H A Dirq-gic.c1338 name = kasprintf(GFP_KERNEL, "GICv2"); in __gic_init_bases()
1404 * first page of a GICv2. in gic_check_eoimode()
1410 pr_warn("GIC: GICv2 detected, but range too small and irqchip.gicv2_force_probe not set\n"); in gic_check_eoimode()
1419 * The first page was that of a GICv2, and in gic_check_eoimode()
1421 * to be a GICv2, and update the mapping. in gic_check_eoimode()
1423 pr_warn("GIC: GICv2 at %pa, but range is too small (broken DT?), assuming 8kB\n", in gic_check_eoimode()
1431 * We detected *two* initial GICv2 pages in a in gic_check_eoimode()
1432 * row. Could be a GICv2 aliased over two 64kB in gic_check_eoimode()
1440 pr_warn("GIC: Aliased GICv2 at %pa, trying to find the canonical range over 128kB\n", in gic_check_eoimode()
1448 * Verify that we have the first 4kB of a GICv2 in gic_check_eoimode()
[all …]
/OK3568_Linux_fs/u-boot/arch/arm/lib/
H A Dgic_64.S69 * For Gicv2:
208 * For Gicv2:
229 * For Gicv2:
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dbcm2711.dtsi13 interrupt-parent = <&gicv2>;
56 gicv2: interrupt-controller@40041000 { label
538 interrupt-map = <0 0 0 1 &gicv2 GIC_SPI 143
540 <0 0 0 2 &gicv2 GIC_SPI 144
542 <0 0 0 3 &gicv2 GIC_SPI 145
544 <0 0 0 4 &gicv2 GIC_SPI 146
/OK3568_Linux_fs/u-boot/drivers/irq/
H A DKconfig3 depends on GICV2 || GICV3
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/interrupt-controller/
H A Darm,gic.yaml93 For GICv2 with virtualization extensions, additional regions are
194 // GICv2
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/gpio/
H A Dgpio-xgene-sb.txt12 | (GICv2) +--------------+ +------ GPIO_[N+8]/EXT_INT_N
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/pci/
H A Dbrcm,stb-pcie.yaml132 interrupt-map = <0 0 0 1 &gicv2 GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH>;
/OK3568_Linux_fs/kernel/arch/arm64/kvm/hyp/
H A Dvgic-v3-sr.c264 * Group0 interrupt (as generated in GICv2 mode) to be in __vgic_v3_activate_traps()
412 * - [63] MMIO (GICv2) capable
420 * To check whether we have a MMIO-based (GICv2 compatible) in __vgic_v3_get_gic_config()
/OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/arm64/
H A Dbooting.txt205 - 设备树(DT)或 ACPI 表必须描述一个 GICv2 中断控制器。
/OK3568_Linux_fs/kernel/include/linux/irqchip/
H A Darm-gic-v3.h50 * Those registers are actually from GICv2, but the spec demands that they
594 /* These are for GICv2 emulation only */
/OK3568_Linux_fs/kernel/Documentation/arm64/
H A Dmemory.rst102 GICv2 gets mapped next to the HYP idmap page, as do vectors when

123