mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-27 00:05:11 +07:00
6c7a2676f5
As has been discussed many times[1], Using NO_IRQ set to anything other than 0 is bug waiting to happen since many drivers follow the pattern "if (!irq)" for testing whether or not an irq has been set. This patch changes the Microblaze NO_IRQ setting from -1 to 0 to bring it in line with most of the rest of the kernel. It also prepares for Microblaze eventually supporting multiple interrupt controllers by breaking the assumption that hwirq# == Linux IRQ#. The Linux IRQ number is just a cookie with no guarantee of a direct relationship with the hardware irq arrangement. At this point, Microblaze interrupt handling only supports only one instance of one kind of interrupt controller (xilinx_intc). This change shouldn't affect any architecture code outside of the interrupt controller driver and the irq_of mapping. Updated to 3.2 and to use irq_data.hwirq by Rob Herring. Tested and fixed by Michal Simek. [1] http://lkml.org/lkml/2005/11/21/221 Signed-off-by: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Rob Herring <rob.herring@calxeda.com> Signed-off-by: Michal Simek <monstr@monstr.eu> |
||
|---|---|---|
| .. | ||
| cpu | ||
| asm-offsets.c | ||
| dma.c | ||
| early_printk.c | ||
| entry-nommu.S | ||
| entry.S | ||
| exceptions.c | ||
| ftrace.c | ||
| head.S | ||
| heartbeat.c | ||
| hw_exception_handler.S | ||
| init_task.c | ||
| intc.c | ||
| irq.c | ||
| kgdb.c | ||
| Makefile | ||
| mcount.S | ||
| microblaze_ksyms.c | ||
| misc.S | ||
| module.c | ||
| process.c | ||
| prom_parse.c | ||
| prom.c | ||
| ptrace.c | ||
| reset.c | ||
| selfmod.c | ||
| setup.c | ||
| signal.c | ||
| stacktrace.c | ||
| sys_microblaze.c | ||
| syscall_table.S | ||
| timer.c | ||
| traps.c | ||
| unwind.c | ||
| vmlinux.lds.S | ||