| /Zephyr-latest/soc/renesas/ra/ra6e2/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra4e1/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra4e2/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra8m1/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra8t1/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra6m4/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra6m5/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra8d1/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/soc/renesas/ra/ra4l1/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | intc_intel_vtd.h | 35 uint64_t vector : 8; member
|
| /Zephyr-latest/soc/nxp/rw/ |
| D | Kconfig | 46 hex "Image vector table offset"
|
| /Zephyr-latest/tests/arch/arc/arc_dsp_sharing/ |
| D | README.txt | 8 2) compute complex vector product and check for any errors
|
| /Zephyr-latest/arch/arm/core/cortex_m/ |
| D | Kconfig | 137 The VTOR indicates the offset of the vector table base
173 the vector table to SRAM
354 vector table relay handler and a vector relay table, to
355 relay interrupts based on a vector table pointer.
357 with no hardware vector table relocation mechanisms (e.g. VTOR).
366 sure the vector table pointer in RAM is set properly by the image upon
|
| /Zephyr-latest/soc/renesas/ra/ra2l1/ |
| D | sections.ld | 9 /* If DTC is used, put the DTC vector table at the start of SRAM.
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 29 An :abbr:`IDT (Interrupt Descriptor Table)` or a vector table is used
525 gen_isr_tables.py script to generate a C file defining a vector table and
537 A vector table is generated when :kconfig:option:`CONFIG_GEN_IRQ_VECTOR_TABLE` is
553 common entry point for all interrupts and do not support a vector table, in
679 The x86 architecture has a special type of vector table called the Interrupt
681 processor documentation. It is still fundamentally a vector table, and the
683 systems the indexes in the vector table do not correspond to the IRQ line. The
688 configures an interrupt it will look for a free vector in the appropriate range
691 On x86 when an interrupt or exception vector is executed by the CPU, there is
692 no foolproof way to determine which vector was fired, so a software ISR table
[all …]
|
| /Zephyr-latest/soc/sensry/ganymed/sy1xx/common/ |
| D | linker.ld | 26 * jumping distance of the vector table in non-XIP builds, so avoid them.
104 * zephyr_linker_sources(ROM_START ...). This typically contains the vector
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 492 an appropriate hardware vector table and/or software IRQ table.
495 bool "Generate an interrupt vector table"
500 needs an interrupt vector table created. Only disable this if the
501 platform does not use a vector table at all, or requires the vector
503 indexed by IRQ line. In the latter case, the vector table must be
507 int "Alignment size of the interrupt vector table"
512 _irq_vector_table. Some architecture needs an IRQ vector table
517 prompt "IRQ vector table type"
525 The IRQ vector table contains the address of the interrupt handler.
530 The IRQ vector table contains the opcode of a jump instruction to the
[all …]
|
| /Zephyr-latest/soc/infineon/cat1b/cyw20829/ |
| D | bootstrap.ld | 21 * zephyr_linker_sources(ROM_START ...). This typically contains the vector
|
| /Zephyr-latest/dts/riscv/openisa/ |
| D | rv32m1_zero_riscy.dtsi | 26 * these base addresses contain the Arm core vector tables if
|
| D | rv32m1_ri5cy.dtsi | 26 * these base addresses contain the Arm core vector tables if
|
| /Zephyr-latest/drivers/virtualization/ |
| D | Kconfig | 40 MSI-X vector holders must be pre-allocated. One can pre-allocate
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | arch.h | 35 uint8_t vector; member
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico2/ |
| D | rpi_pico2.dtsi | 71 * smaller than 256 bytes, but in practice the linker places the vector
|
| /Zephyr-latest/boards/renesas/rzt2m_starterkit/doc/ |
| D | index.rst | 50 | NVIC | on-chip | nested vector interrupt controller |
|
| /Zephyr-latest/subsys/net/l2/ethernet/gptp/ |
| D | gptp_mi.c | 1318 struct gptp_priority_vector *vector, in compare_priority_vectors() argument
1330 &vector->root_system_id, in compare_priority_vectors()
1339 spi_cmp = memcmp(&hdr->port_id, &vector->src_port_id, in compare_priority_vectors()
1342 port_cmp = (int)port - ntohs(vector->port_number); in compare_priority_vectors()
1407 static void copy_priority_vector(struct gptp_priority_vector *vector, in copy_priority_vector() argument
1416 memcpy(&vector->root_system_id, &announce->root_system_id, in copy_priority_vector()
1419 memcpy(&vector->src_port_id, &hdr->port_id, in copy_priority_vector()
1422 vector->port_number = htons(port); in copy_priority_vector()
|
