Home
last modified time | relevance | path

Searched refs:vector (Results 76 – 100 of 479) sorted by relevance

12345678910>>...20

/Zephyr-latest/include/zephyr/arch/x86/ia32/
Darch.h220 [vector] "i" _VECTOR_ARG(irq_p), \
363 : [vector] "i" (Z_X86_OOPS_VECTOR), \
/Zephyr-latest/soc/openisa/rv32m1/
DCMakeLists.txt12 vector.S
Dvector_table.ld16 * For CONFIG_BOOTLOADER_MCUBOOT, the vector table is located at the
/Zephyr-latest/drivers/pcie/host/
DKconfig51 bool "MSI multi-vector support"
54 support of such capability so each message can get a vector
66 if you want to support multi-vector on MSI-X as well.
Dpcie.c341 msi_vector_t vector; in pcie_connect_dynamic_irq() local
344 &vector, 1) == 0) || in pcie_connect_dynamic_irq()
345 !pcie_msi_vector_connect(bdf, &vector, in pcie_connect_dynamic_irq()
/Zephyr-latest/include/zephyr/arch/sparc/
Darch.h118 : [vector] "i" (SPARC_SW_TRAP_EXCEPT), "r" (_g1) \
/Zephyr-latest/tests/arch/arc/arc_vpx_lock/
DREADME.txt6 code that uses the ARC VPX vector registers works correctly. As this VPX
/Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/
DREADME.rst156 int <peer> <vector>: notify one vector on a peer
162 vector 0 is enabled (fd=7)
163 vector 1 is enabled (fd=8)
165 vector 0 is enabled (fd=5)
166 vector 1 is enabled (fd=6)
/Zephyr-latest/tests/modules/thrift/ThriftTest/src/
Dclient.cpp151 vector<int32_t> response_list; in ZTEST()
152 context.client->testList(response_list, vector<int32_t>()); in ZTEST()
155 static const vector<int32_t> request_list = {-2, -1, 0, 1, 2}; in ZTEST()
/Zephyr-latest/arch/x86/
Dgen_idt.py118 def update_irq_vec_map(irq_vec_map, irq, vector, max_irq): argument
132 debug("assign IRQ %d to vector %d" % (irq, vector))
133 irq_vec_map[irq] = vector
/Zephyr-latest/drivers/virtualization/
Dvirt_ivshmem.h43 uint8_t vector; member
/Zephyr-latest/drivers/interrupt_controller/
Dintc_loapic.c205 unsigned int vector /* vector to copy into the LVT */ in z_loapic_int_vec_set() argument
228 ~LOAPIC_VECTOR) | vector); in z_loapic_int_vec_set()
/Zephyr-latest/arch/nios2/
DKconfig45 bool "Include Reset vector"
48 Include the reset vector stub, which enables instruction/data caches
/Zephyr-latest/tests/arch/x86/static_idt/
DREADME.txt25 ***** Unhandled interrupt vector *****
/Zephyr-latest/doc/hardware/arch/
Darc-support-status.rst92 .. [#f6] currently only ARC VPX scalar port is supported. The support of VPX vector pipeline, VCCM,
98 Zephyr supports a limited form sharing of the VPX vector registers known as
112 The cooperative sharing of the VPX vector registers is selected when
/Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/
DREADME.txt5 This test verifies that the vector table relay feature
/Zephyr-latest/arch/xtensa/
DKconfig18 bool "Build reset vector code"
21 This option controls whether the initial reset vector code is built.
50 bool "Workaround for small vector table entries"
53 constraint of the vector table entry and moved the default
54 handlers to the end of vector table, renaming them to
/Zephyr-latest/arch/x86/core/
DKconfig.intel6444 int "IDT vector to use for scheduler IPI"
50 int "IDT vector to use for TLB shootdown IPI"
/Zephyr-latest/soc/snps/emsk/
Dlinker.ld16 * DRAM includes the exception vector table at reset, which is at
/Zephyr-latest/soc/renesas/ra/ra4m2/
Dsections.ld17 /* If DTC is used, put the DTC vector table at the start of SRAM.
/Zephyr-latest/soc/renesas/ra/ra4m3/
Dsections.ld17 /* If DTC is used, put the DTC vector table at the start of SRAM.
/Zephyr-latest/soc/renesas/ra/ra6e1/
Dsections.ld17 /* If DTC is used, put the DTC vector table at the start of SRAM.
/Zephyr-latest/soc/renesas/ra/ra6m4/
Dsections.ld17 /* If DTC is used, put the DTC vector table at the start of SRAM.
/Zephyr-latest/soc/renesas/ra/ra6m5/
Dsections.ld17 /* If DTC is used, put the DTC vector table at the start of SRAM.
/Zephyr-latest/soc/renesas/ra/ra8d1/
Dsections.ld17 /* If DTC is used, put the DTC vector table at the start of SRAM.

12345678910>>...20