diff options
author | Arnd Bergmann <arnd@arndb.de> | 2025-02-05 13:11:33 +0100 |
---|---|---|
committer | Arnd Bergmann <arnd@arndb.de> | 2025-03-06 16:36:03 +0100 |
commit | 98f3ab18a0a55aa1ff2cd6b74bd0c02c8f76f17e (patch) | |
tree | 81eaddbc16741080342ca176ff1aa0b9525deb52 /include/linux/fpga/fpga-bridge.h | |
parent | 26e29a26f84a7dc88e69f3b164753127a2b2cd23 (diff) |
ARM: OMAP1: select CONFIG_GENERIC_IRQ_CHIP
When GENERIC_IRQ_CHIP is disabled, OMAP1 kernels fail to link:
arm-linux-gnueabi-ld: arch/arm/mach-omap1/irq.o: in function `omap1_init_irq':
irq.c:(.init.text+0x1e8): undefined reference to `irq_alloc_generic_chip'
arm-linux-gnueabi-ld: irq.c:(.init.text+0x228): undefined reference to `irq_setup_generic_chip'
arm-linux-gnueabi-ld: irq.c:(.init.text+0x2a8): undefined reference to `irq_gc_set_wake'
arm-linux-gnueabi-ld: irq.c:(.init.text+0x2b0): undefined reference to `irq_gc_mask_set_bit'
arm-linux-gnueabi-ld: irq.c:(.init.text+0x2b4): undefined reference to `irq_gc_mask_clr_bit'
This has apparently been the case for many years, but I never caught it
in randconfig builds until now, as there are dozens of other drivers
that also 'select GENERIC_IRQ_CHIP' and statistically there is almost
always one of them enabled.
Fixes: 55b447744389 ("ARM: OMAP1: Switch to use generic irqchip in preparation for sparse IRQ")
Link: https://lore.kernel.org/r/20250205121151.289535-1-arnd@kernel.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'include/linux/fpga/fpga-bridge.h')
0 files changed, 0 insertions, 0 deletions