-
CONFIG_GEN_ISR_TABLES
¶
Use generated IRQ tables
Type: bool
Help¶
This option controls whether a platform uses the gen_isr_tables script to generate its interrupt tables. This mechanism will create an appropriate hardware vector table and/or software IRQ table.
Defaults¶
y
y
y
y
y
y
Kconfig definitions¶
At arch/arc/Kconfig:195
Included via Kconfig:8
→ Kconfig.zephyr:29
→ arch/Kconfig:12
Menu path: (Top) → ARC Options → ARCv2 Family Options
config GEN_ISR_TABLES
bool
default y
depends on ARC
At arch/arm/core/aarch32/cortex_m/Kconfig:238
Included via Kconfig:8
→ Kconfig.zephyr:29
→ arch/Kconfig:12
→ arch/arm/Kconfig:9
→ arch/arm/core/aarch32/Kconfig:272
Menu path: (Top) → ARM Options → ARM Cortex-M0/M0+/M3/M4/M7/M23/M33 options
config GEN_ISR_TABLES bool default y depends on (ARMV6_M_ARMV8_M_BASELINE
||ARMV7_M_ARMV8_M_MAINLINE
) &&CPU_CORTEX_M
&& !ARM64
&&ARM
At arch/arm/core/aarch32/cortex_r/Kconfig:81
Included via Kconfig:8
→ Kconfig.zephyr:29
→ arch/Kconfig:12
→ arch/arm/Kconfig:9
→ arch/arm/core/aarch32/Kconfig:273
Menu path: (Top) → ARM Options
config GEN_ISR_TABLES bool default y depends onCPU_CORTEX_R
&& !ARM64
&&ARM
At arch/arm/core/aarch64/Kconfig:87
Included via Kconfig:8
→ Kconfig.zephyr:29
→ arch/Kconfig:12
→ arch/arm/Kconfig:10
Menu path: (Top) → ARM Options
config GEN_ISR_TABLES bool default y depends onCPU_CORTEX_A
&&ARM64
&&ARM
At arch/nios2/Kconfig:27
Included via Kconfig:8
→ Kconfig.zephyr:29
→ arch/Kconfig:12
Menu path: (Top) → Nios II Options → Nios II Family Options
config GEN_ISR_TABLES
bool
default y
depends on NIOS2
At arch/riscv/Kconfig:86
Included via Kconfig:8
→ Kconfig.zephyr:29
→ arch/Kconfig:12
Menu path: (Top) → RISCV Options → RISCV Processor Options
config GEN_ISR_TABLES
bool
default y
depends on RISCV
At arch/Kconfig:295
Included via Kconfig:8
→ Kconfig.zephyr:29
Menu path: (Top) → General Architecture Options → Interrupt Configuration
config GEN_ISR_TABLES
bool "Use generated IRQ tables"
help
This option controls whether a platform uses the gen_isr_tables
script to generate its interrupt tables. This mechanism will create
an appropriate hardware vector table and/or software IRQ table.
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)