CONFIG_GEN_IRQ_VECTOR_TABLE

Generate an interrupt vector table

Type: bool

Help

This option controls whether a platform using gen_isr_tables needs an interrupt vector table created. Only disable this if the platform does not use a vector table at all, or requires the vector table to be in a format that is not an array of function pointers indexed by IRQ line. In the latter case, the vector table must be supplied by the application or architecture code.

Direct dependencies

(CPU_CORTEX_R && CPU_CORTEX_R && ARM) || NIOS2 || RISCV || GEN_ISR_TABLES

(Includes any dependencies from ifs and menus.)

Defaults

  • n

  • n

  • n

  • y

Kconfig definitions

At arch/arm/core/aarch32/cortex_r/Kconfig:86

Included via Kconfig:8Kconfig.zephyr:34arch/Kconfig:12arch/arm/Kconfig:9arch/arm/core/aarch32/Kconfig:271

Menu path: (Top) → ARM Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on CPU_CORTEX_R && CPU_CORTEX_R && ARM

At arch/nios2/Kconfig:30

Included via Kconfig:8Kconfig.zephyr:34arch/Kconfig:12

Menu path: (Top) → Nios II Options → Nios II Family Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on NIOS2

At arch/riscv/Kconfig:89

Included via Kconfig:8Kconfig.zephyr:34arch/Kconfig:12

Menu path: (Top) → RISCV Options → RISCV Processor Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on RISCV

At arch/Kconfig:272

Included via Kconfig:8Kconfig.zephyr:34

Menu path: (Top) → General Architecture Options → Interrupt Configuration → Use generated IRQ tables

config GEN_IRQ_VECTOR_TABLE
    bool "Generate an interrupt vector table"
    default y
    depends on GEN_ISR_TABLES
    help
      This option controls whether a platform using gen_isr_tables
      needs an interrupt vector table created. Only disable this if the
      platform does not use a vector table at all, or requires the vector
      table to be in a format that is not an array of function pointers
      indexed by IRQ line. In the latter case, the vector table must be
      supplied by the application or architecture code.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)