b5908fd89d
Platforms which use the GEN_SW_ISR mechanism for interrupt handling can make use of a really simple whitebox trick for verifying that it worked (i.e. that the pointer and argument get placed in the table correctly). Easy and simple way to get some coverage for dynamic IRQs, which is currently entirely missing. Long term we'll want to replace this with a test that uses the API directly and chooses an arch-specific vector to set, and triggers it using arch-specific code, but that's quite a bit more effort and for now we need to land patches to z_irq_connect_dynamic() which show test coverage. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
15 lines
533 B
YAML
15 lines
533 B
YAML
tests:
|
|
arch.interrupt:
|
|
arch_exclude: nios2 riscv32 arc qemu_x86 qemu_x86_coverage qemu_x86_64
|
|
platform_exclude: hexiwear_kw40z frdm_kw41z frdm_kl25z nucleo_f103rb
|
|
nucleo_f091rc olimexino_stm32 usb_kw24d512 stm32_min_dev_blue
|
|
stm32_min_dev_black v2m_beetle
|
|
tags: interrupt
|
|
|
|
# Platforms without relevant (gen isr) dynamic interrupt support:
|
|
arch.interrupt.nodyn:
|
|
arch_whitelist: arc qemu_x86 qemu_x86_coverage qemu_x86_64
|
|
tags: interrupt
|
|
extra_configs:
|
|
- CONFIG_DYNAMIC_INTERRUPTS=n
|