[PATCH v2 00/11] irqdomain: Refactor

From: Grant Likely
Date: Fri Jun 14 2013 - 17:08:17 EST

I've done a bunch of refactoring work on the irq_domain infrastructure.
Some of these patches I've posted before, and some our brand new. The
goal of this is to greatly simplify how irq_domains work. With this
series, instead of there being multiple different types of irq domains,
each with different mapping rules, instead there is now only one time of
irq_domain that contains both kinds of map; the linear map for irqs
below a certain value, and the radix tree for large & sparse irq
controllers. As you can see from the following diffstat, the result is a
fair bit less code. It should make it easier to understand irqdomains

This is the second posting of this series. I've added a couple more
patches and dropped an unrelated patch to the versatile irq driver.

irqdomain: Relax failure path on setting up mappings
irqdomain: Replace LEGACY mapping with LINEAR
irqdomain: Add a name field
irqdomain: merge linear and tree reverse mappings.
irqdomain: Eliminate revmap type
irqdomain: Clean up aftermath of irq_domain refactoring
irqdomain: Beef up debugfs output
irqdomain: Refactor irq_domain_associate_many()
irqdomain: remove irq_domain_generate_simple()
irqdomain: make irq_linear_revmap() a fast path again
irqdomain: Include hwirq number in /proc/interrupts

arch/powerpc/platforms/cell/beat_interrupt.c | 2 +-
arch/powerpc/platforms/powermac/smp.c | 2 +-
arch/x86/kernel/devicetree.c | 4 +-
include/linux/irqdomain.h | 142 +++++++------
kernel/irq/generic-chip.c | 6 +-
kernel/irq/irqdomain.c | 571 ++++++++++++++++----------------------------------
kernel/irq/proc.c | 2 +
7 files changed, 261 insertions(+), 468 deletions(-)

I've pushed this series out to my git server at the following branch:

git://git.secretlab.ca/git/linux irqdomain/test

It depends on the tip tree's irq/for-arm branch and also Linus' mainline
(they need to be merged). The branch above includes both.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/