gpio: fix sleep-while-atomic in gpiochip_remove
authorJohan Hovold <johan@kernel.org>
Mon, 12 Jan 2015 16:12:28 +0000 (17:12 +0100)
committerLinus Walleij <linus.walleij@linaro.org>
Wed, 14 Jan 2015 13:26:25 +0000 (14:26 +0100)
Move direct and indirect calls to gpiochip_remove_pin_ranges outside of
spin lock as they can end up taking a mutex in pinctrl_remove_gpio_range.

Note that the pin ranges are already added outside of the lock.

Fixes: 9ef0d6f7628b ("gpiolib: call pin removal in chip removal function")
Fixes: f23f1516b675 ("gpiolib: provide provision to register pin ranges")
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
drivers/gpio/gpiolib.c

index 0f8173051edca39f654a6069126927516f4182da..37f919dc2cb47832455e09a8c282e21616607c1c 100644 (file)
@@ -330,12 +330,10 @@ void gpiochip_remove(struct gpio_chip *chip)
        gpiochip_irqchip_remove(chip);
 
        acpi_gpiochip_remove(chip);
-
-       spin_lock_irqsave(&gpio_lock, flags);
-
        gpiochip_remove_pin_ranges(chip);
        of_gpiochip_remove(chip);
 
+       spin_lock_irqsave(&gpio_lock, flags);
        for (id = 0; id < chip->ngpio; id++) {
                if (test_bit(FLAG_REQUESTED, &chip->desc[id].flags))
                        dev_crit(chip->dev, "REMOVING GPIOCHIP WITH GPIOS STILL REQUESTED\n");