Home
last modified time | relevance | path

Searched refs:vector (Results 126 – 150 of 294) sorted by relevance

12345678910>>...12

/Zephyr-4.1.0/doc/services/binary_descriptors/
Dindex.rst38 possible. In architectures where the image must begin with a vector table (such as
39 ARM), the descriptors are linked right after the vector table. The reset vector points
/Zephyr-4.1.0/arch/arc/
DKconfig154 The minimum value is 17 as the first 16 entries in the vector
158 vector table.
347 bool "Cooperative sharing of ARC VPX vector registers"
350 This option enables the cooperative sharing of the ARC VPX vector
/Zephyr-4.1.0/boards/pimoroni/pico_plus2/
Dpico_plus2.dtsi102 * smaller than 256 bytes, but in practice the linker places the vector
/Zephyr-4.1.0/drivers/disk/nvme/
DKconfig11 driver to support these. It will enable MSI-X and MSI multi-vector
Dnvme_controller_cmd.c82 cmd->cdw11 = sys_cpu_to_le32((io_queue->vector << 16) | 0x3); in nvme_ctrlr_cmd_create_io_cq()
Dnvme_cmd.c493 qpair->vector = qpair->id; in nvme_cmd_qpair_setup()
510 &ctrlr->vectors[qpair->vector], in nvme_cmd_qpair_setup()
/Zephyr-4.1.0/arch/x86/
Dia32.cmake112 --vector-map irq_int_vector_map.bin
/Zephyr-4.1.0/include/zephyr/arch/
Darch_interface.h1242 bool arch_pcie_msi_vector_connect(msi_vector_t *vector,
/Zephyr-4.1.0/boards/arm/v2m_beetle/doc/
Dindex.rst57 | NVIC | on-chip | nested vector interrupt controller |
89 calls a handler directly from the vector table.
/Zephyr-4.1.0/doc/hardware/arch/
Darm_cortex_m.rst79 | SW-based vector table relaying | | Y | Y |…
584 Software vector relaying
588 chain-loadable images relocate the Cortex-M vector table by updating the VTOR register with the off…
589 of the image vector table.
592 vector table which remains at a fixed location. Therefore, a chain-loadable image will
593 require an alternative way to route HW interrupts and system exceptions to its own vector
594 table; this is achieved with software vector relaying.
597 it is able to relay exceptions and interrupts based on a vector table
600 sequence to set the vector table pointer in SRAM so that the bootloader can
602 vector table.
/Zephyr-4.1.0/drivers/timer/
Dapic_tsc.c83 uint8_t vector : 8; member
DKconfig.x8678 local vector table). This footgun is not intended to be
/Zephyr-4.1.0/samples/bluetooth/encrypted_advertising/
DREADME.rst12 - the exchange of the session key and the initialization vector using the Key
/Zephyr-4.1.0/boards/lowrisc/opentitan_earlgrey/doc/
Dindex.rst35 | NVIC | on-chip | nested vector interrupt controller |
/Zephyr-4.1.0/arch/common/
DCMakeLists.txt55 ${ZEPHYR_BASE}/include/zephyr/linker/irq-vector-table-section.ld
/Zephyr-4.1.0/dts/arm/st/f1/
Dstm32f103Xc.dtsi125 /* Shares vector with ADC1 */
/Zephyr-4.1.0/boards/arm/mps2/doc/
Dmps2_armv6m.rst69 | NVIC | on-chip | nested vector interrupt controller |
98 calls a handler directly from the vector table.
Dmps2_armv7m.rst76 | NVIC | on-chip | nested vector interrupt controller |
106 calls a handler directly from the vector table.
/Zephyr-4.1.0/arch/xtensa/core/
DREADME_MMU.txt128 Ideally we would just pin the vector/handler page in the ITLB in the
133 Instead, we load ITLB entries for vector handlers via the refill
135 vector page to succeed always. The way to do this is to similarly pin
136 the page table page containing the (single) PTE for the vector page in
192 (Pedantic note: if the vector page and the currently-executing page
DCMakeLists.txt108 # Auto-generate interrupt vector entry
/Zephyr-4.1.0/boards/sc/scobc_module1/doc/
Dindex.rst29 | NVIC | on-chip | nested vector interrupt controller |
/Zephyr-4.1.0/boards/waveshare/esp32s3_touch_lcd_1_28/doc/
Dindex.rst21 - Additional vector instructions support for AI acceleration
/Zephyr-4.1.0/doc/services/storage/disk/
Dnvme.rst63 Note that NVME requires the target to support PCIe multi-vector MSI-X in order to function.
/Zephyr-4.1.0/include/zephyr/arch/mips/
Dlinker.ld21 #define _VECTOR_SECTION_NAME vector
/Zephyr-4.1.0/include/zephyr/arch/arm/cortex_a_r/scripts/
Dlinker.ld29 /* Region of the irq vectors and boot-vector SP/PC */
131 * zephyr_linker_sources(ROM_START ...). This typically contains the vector

12345678910>>...12