This is the documentation for the latest (master) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.
CONFIG_MULTI_LEVEL_INTERRUPTS

Multi-level interrupt support

Type: bool

Help

Multiple levels of interrupts are normally used to increase the number of addressable interrupts in a system. For example, if two levels are used, a second level interrupt aggregator would combine all interrupts routed to it into one IRQ line in the first level interrupt controller. If three levels are used, a third level aggregator combines its input interrupts into one IRQ line at the second level. The number of interrupt levels is usually determined by the hardware. (The term “aggregator” here means “interrupt controller”.)

Direct dependencies

SOC_INTEL_APL_ADSP || GEN_SW_ISR_TABLE

(Includes any dependencies from ifs and menus.)

Default

  • y

Symbols that select this symbol

Kconfig definitions

At soc/xtensa/intel_apl_adsp/Kconfig.defconfig:27

Included via Kconfig:8Kconfig.zephyr:25doc/_build/Kconfig/Kconfig.soc.defconfig:1

Menu path: (Top)

config MULTI_LEVEL_INTERRUPTS
    bool
    default y
    depends on SOC_INTEL_APL_ADSP

At drivers/interrupt_controller/Kconfig.multilevel:7

Included via Kconfig:8Kconfig.zephyr:32drivers/Kconfig:24drivers/interrupt_controller/Kconfig:42

Menu path: (Top) → Device Drivers → Interrupt Controllers

config MULTI_LEVEL_INTERRUPTS
    bool "Multi-level interrupt support"
    depends on GEN_SW_ISR_TABLE
    help
      Multiple levels of interrupts are normally used to increase the
      number of addressable interrupts in a system. For example, if two
      levels are used, a second level interrupt aggregator would combine
      all interrupts routed to it into one IRQ line in the first level
      interrupt controller. If three levels are used, a third level
      aggregator combines its input interrupts into one IRQ line at the
      second level. The number of interrupt levels is usually determined
      by the hardware. (The term "aggregator" here means "interrupt
      controller".)

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