gpiolib: fix chip order in gpio list

In some situations the gpio_list order is not correct.
As a consequence gpiochip_find_base returns the same
base number twice. This happens when a first ship is added
with manual base number, then other ships are added using
automatic base number.

To prevent this behaviour, this patch add the new chip after
the last element of the gpio list.

Signed-off-by: Julien Grossholtz <julien.grossholtz@savoirfairelinux.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 3db34e74bc340a86e7d17099e6c747bc38c0175e..a1805734aef87b212b4b4f8ea28c1f97e2ea561e 100644 (file)
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -226,8 +226,10 @@ static int gpiochip_add_to_list(struct gpio_chip *chip)
         */
 
        iterator = list_last_entry(&gpio_chips, struct gpio_chip, list);
-       if (iterator->base + iterator->ngpio <= chip->base)
-               goto found;
+       if (iterator->base + iterator->ngpio <= chip->base) {
+               list_add(&chip->list, &iterator->list);
+               return 0;
+       }
 
        dev_err(chip->parent,
               "GPIO integer space overlap, cannot add chip\n");