The MXS driver tries to do the work of irq_domain_add_linear()
by reserving a bunch of descriptors somewhere and keeping track
of the base offset, then calling irq_domain_add_legacy(). Let's
stop doing that and simply use the linear IRQ domain.

Cc: Rob Herring <rob.herr...@calxeda.com>
Cc: Grant Likely <grant.lik...@secretlab.ca>
Cc: Stephen Warren <swar...@nvidia.com>
Signed-off-by: Linus Walleij <linus.wall...@linaro.org>
---
 drivers/gpio/gpio-tegra.c | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/drivers/gpio/gpio-tegra.c b/drivers/gpio/gpio-tegra.c
index d982593..0234162 100644
--- a/drivers/gpio/gpio-tegra.c
+++ b/drivers/gpio/gpio-tegra.c
@@ -380,7 +380,6 @@ static int __devinit tegra_gpio_probe(struct 
platform_device *pdev)
 {
        const struct of_device_id *match;
        struct tegra_gpio_soc_config *config;
-       int irq_base;
        struct resource *res;
        struct tegra_gpio_bank *bank;
        int gpio;
@@ -417,14 +416,11 @@ static int __devinit tegra_gpio_probe(struct 
platform_device *pdev)
                return -ENODEV;
        }
 
-       irq_base = irq_alloc_descs(-1, 0, tegra_gpio_chip.ngpio, 0);
-       if (irq_base < 0) {
-               dev_err(&pdev->dev, "Couldn't allocate IRQ numbers\n");
-               return -ENODEV;
-       }
-       irq_domain = irq_domain_add_legacy(pdev->dev.of_node,
-                                          tegra_gpio_chip.ngpio, irq_base, 0,
+       irq_domain = irq_domain_add_linear(pdev->dev.of_node,
+                                          tegra_gpio_chip.ngpio,
                                           &irq_domain_simple_ops, NULL);
+       if (!irq_domain)
+               return -ENODEV;
 
        for (i = 0; i < tegra_gpio_bank_count; i++) {
                res = platform_get_resource(pdev, IORESOURCE_IRQ, i);
-- 
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/

Reply via email to