[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1452203205-4660-1-git-send-email-julien.grossholtz@savoirfairelinux.com>
Date: Thu, 7 Jan 2016 16:46:45 -0500
From: Julien Grossholtz <julien.grossholtz@...oirfairelinux.com>
To: linus.walleij@...aro.org, gnurou@...il.com
Cc: linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...oirfairelinux.com, bamvor.zhangjian@...aro.org,
Julien Grossholtz <julien.grossholtz@...oirfairelinux.com>
Subject: [PATCH] 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 ship after
the last element of the gpio list.
Signed-off-by: Julien Grossholtz <julien.grossholtz@...oirfairelinux.com>
---
drivers/gpio/gpiolib.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 3db34e7..a180573 100644
--- 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");
--
2.5.0
Powered by blists - more mailing lists