Searched refs:EOI (Results 1 – 10 of 10) sorted by relevance
/linux-4.4.14/Documentation/virtual/kvm/ |
D | msr.txt | 244 injection. Value of 1 means that guest can skip writing EOI to the apic 246 EOI by clearing the bit in guest memory - this location will 248 Value of 0 means that the EOI write is required. 251 the APIC EOI write anyway. 262 whether it can skip EOI apic write and between guest 263 clearing it to signal EOI to the hypervisor,
|
D | api.txt | 2329 as from an EOI, the gsi is de-asserted and the user is notified via 3327 Indicates that the VCPU's in-kernel local APIC received an EOI for a 3330 the userspace IOAPIC should process the EOI and retrigger the interrupt if 3332 EOI was received. 3666 for the IOAPIC pins. Whenever the LAPIC receives an EOI for these routes,
|
/linux-4.4.14/drivers/media/platform/s5p-jpeg/ |
D | jpeg-core.h | 48 #define EOI 0xd9 macro
|
D | jpeg-core.c | 1193 case EOI: in s5p_jpeg_parse_hdr()
|
/linux-4.4.14/Documentation/virtual/kvm/arm/ |
D | vgic-mapped-irqs.txt | 62 - On guest EOI, the *physical distributor* active bit gets cleared, 74 configures the physical GIC with EOIMode=1, which causes EOI operations to
|
/linux-4.4.14/drivers/media/platform/ |
D | rcar_jpu.c | 82 #define EOI 0xd9 macro 623 if (size < JPU_JPEG_MIN_SIZE || *(u8 *)(buffer + size - 1) != EOI) in jpu_parse_hdr()
|
/linux-4.4.14/Documentation/thermal/ |
D | intel_powerclamp.txt | 208 EOI for level triggered interrupts. But it is a challenge to be
|
/linux-4.4.14/arch/x86/kvm/ |
D | trace.h | 182 AREG(EOI), AREG(RRR), AREG(LDR), AREG(DFR), AREG(SPIV), AREG(ISR), \
|
/linux-4.4.14/drivers/media/usb/gspca/ |
D | cpia1.c | 55 #define EOI 0xff /* End Of Image */ macro
|
/linux-4.4.14/Documentation/ |
D | DMA-API.txt | 619 <EOI> <4>---[ end trace f6435a98e2a38c0e ]---
|