From: Nishanth Menon <nm@ti.com> To: Tony Lindgren <tony@atomide.com>, Linus Walleij <linus.walleij@linaro.org> Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>, Roger Quadros <rogerq@ti.com>, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com> Subject: [PATCH] gpio: twl4030: fix regression for twl gpio outputs for led pins Date: Fri, 13 Dec 2013 10:47:02 -0600 [thread overview] Message-ID: <1386953222-26396-1-git-send-email-nm@ti.com> (raw) Commit 0b2aa8b (gpio: twl4030: Fix regression for twl gpio output) introduces yet another regression by ignoring the fact that we use twl gpio even for LED. For example, leda (offset 18) is used for USB port2 power on beagleboard-xm. The original logic was supposed to setup the TWL4030 GPIO direction if the offset was < TWL4030_GPIO_MAX, and anything greater used twl4030_led_set_value as part of twl_set to setup the LED pin. However, with the commit mentioned above, LEDa pin request will result in fail as the GPIO number for LEDa is equal to TWL4030_GPIO_MAX and USB fails to function on beagleboard-xm. This is reported in the log as: hsusb2_vbus: Failed to request enable GPIO510: -22 To fix this, we should handle the fail case of twl4030_set_gpio_direction independent of the offset < TWL4030_GPIO_MAX check. Signed-off-by: Nishanth Menon <nm@ti.com> --- Applies on v3.13-rc3 Tested on beagleboard-xm which uses ethernet over usb: before the patch (USB regression): http://pastebin.mozilla.org/3769443 After this patch: http://pastebin.mozilla.org/3769454 drivers/gpio/gpio-twl4030.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-twl4030.c b/drivers/gpio/gpio-twl4030.c index b97d6a6..9242276 100644 --- a/drivers/gpio/gpio-twl4030.c +++ b/drivers/gpio/gpio-twl4030.c @@ -354,11 +354,16 @@ static void twl_set(struct gpio_chip *chip, unsigned offset, int value) static int twl_direction_out(struct gpio_chip *chip, unsigned offset, int value) { struct gpio_twl4030_priv *priv = to_gpio_twl4030(chip); - int ret = -EINVAL; + int ret = 0; mutex_lock(&priv->mutex); - if (offset < TWL4030_GPIO_MAX) + if (offset < TWL4030_GPIO_MAX) { ret = twl4030_set_gpio_direction(offset, 0); + if (ret) { + mutex_unlock(&priv->mutex); + return ret; + } + } priv->direction |= BIT(offset); mutex_unlock(&priv->mutex); -- 1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com> To: Tony Lindgren <tony@atomide.com>, Linus Walleij <linus.walleij@linaro.org> Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>, Roger Quadros <rogerq@ti.com>, <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>, Nishanth Menon <nm@ti.com> Subject: [PATCH] gpio: twl4030: fix regression for twl gpio outputs for led pins Date: Fri, 13 Dec 2013 10:47:02 -0600 [thread overview] Message-ID: <1386953222-26396-1-git-send-email-nm@ti.com> (raw) Commit 0b2aa8b (gpio: twl4030: Fix regression for twl gpio output) introduces yet another regression by ignoring the fact that we use twl gpio even for LED. For example, leda (offset 18) is used for USB port2 power on beagleboard-xm. The original logic was supposed to setup the TWL4030 GPIO direction if the offset was < TWL4030_GPIO_MAX, and anything greater used twl4030_led_set_value as part of twl_set to setup the LED pin. However, with the commit mentioned above, LEDa pin request will result in fail as the GPIO number for LEDa is equal to TWL4030_GPIO_MAX and USB fails to function on beagleboard-xm. This is reported in the log as: hsusb2_vbus: Failed to request enable GPIO510: -22 To fix this, we should handle the fail case of twl4030_set_gpio_direction independent of the offset < TWL4030_GPIO_MAX check. Signed-off-by: Nishanth Menon <nm@ti.com> --- Applies on v3.13-rc3 Tested on beagleboard-xm which uses ethernet over usb: before the patch (USB regression): http://pastebin.mozilla.org/3769443 After this patch: http://pastebin.mozilla.org/3769454 drivers/gpio/gpio-twl4030.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-twl4030.c b/drivers/gpio/gpio-twl4030.c index b97d6a6..9242276 100644 --- a/drivers/gpio/gpio-twl4030.c +++ b/drivers/gpio/gpio-twl4030.c @@ -354,11 +354,16 @@ static void twl_set(struct gpio_chip *chip, unsigned offset, int value) static int twl_direction_out(struct gpio_chip *chip, unsigned offset, int value) { struct gpio_twl4030_priv *priv = to_gpio_twl4030(chip); - int ret = -EINVAL; + int ret = 0; mutex_lock(&priv->mutex); - if (offset < TWL4030_GPIO_MAX) + if (offset < TWL4030_GPIO_MAX) { ret = twl4030_set_gpio_direction(offset, 0); + if (ret) { + mutex_unlock(&priv->mutex); + return ret; + } + } priv->direction |= BIT(offset); mutex_unlock(&priv->mutex); -- 1.7.9.5
next reply other threads:[~2013-12-13 16:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-13 16:47 Nishanth Menon [this message] 2013-12-13 16:47 ` [PATCH] gpio: twl4030: fix regression for twl gpio outputs for led pins Nishanth Menon 2013-12-13 17:28 ` Tony Lindgren 2013-12-13 17:36 ` Nishanth Menon 2013-12-13 17:36 ` Nishanth Menon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1386953222-26396-1-git-send-email-nm@ti.com \ --to=nm@ti.com \ --cc=linus.walleij@linaro.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=peter.ujfalusi@ti.com \ --cc=rogerq@ti.com \ --cc=tony@atomide.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.