The MVEBU driver probably just wants a few IRQs. Using the simple
domain has the upside of allocating IRQ descriptors if need be,
especially in a SPARSE_IRQ environment.
Also replace one instance of irq_create_mapping() with
irq_find_mapping(), the domain is registered in probe() so
the irq is sure there to be found, no reason to ask for
on-the-fly remappings here.
Cc: Rob Herring <rob.herr...@calxeda.com>
Cc: Grant Likely <grant.lik...@secretlab.ca>
Cc: Thomas Petazzoni <thomas.petazz...@free-electrons.com>
Cc: Sebastian Hesselbarth <sebastian.hesselba...@gmail.com>
Cc: Andrew Lunn <and...@lunn.ch>
Signed-off-by: Linus Walleij <linus.wall...@linaro.org>
---
drivers/gpio/gpio-mvebu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index 902af43..8fdeed2 100644
--- a/drivers/gpio/gpio-mvebu.c
+++ b/drivers/gpio/gpio-mvebu.c
@@ -257,7 +257,7 @@ static int mvebu_gpio_to_irq(struct gpio_chip *chip,
unsigned pin)
{
struct mvebu_gpio_chip *mvchip =
container_of(chip, struct mvebu_gpio_chip, chip);
- return irq_create_mapping(mvchip->domain, pin);
+ return irq_find_mapping(mvchip->domain, pin);
}
/*
@@ -645,8 +645,8 @@ static int __devinit mvebu_gpio_probe(struct
platform_device *pdev)
IRQ_NOREQUEST, IRQ_LEVEL | IRQ_NOPROBE);
/* Setup irq domain on top of the generic chip. */
- mvchip->domain = irq_domain_add_legacy(np, mvchip->chip.ngpio,
- mvchip->irqbase, 0,
+ mvchip->domain = irq_domain_add_simple(np, mvchip->chip.ngpio,
+ mvchip->irqbase,
&irq_domain_simple_ops,
mvchip);
if (!mvchip->domain) {
--
1.7.11.7
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
