From: Javier Martinez Canillas <javier@dowhile0.org> To: Aaro Koskinen <aaro.koskinen@iki.fi> Cc: Linus Walleij <linus.walleij@linaro.org>, Javier Martinez Canillas <javier.martinez@collabora.co.uk>, Santosh Shilimkar <santosh.shilimkar@ti.com>, Kevin Hilman <khilman@linaro.org>, Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>, Nishanth Menon <nm@ti.com>, "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, Linux-OMAP <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 0/5] GPIO OMAP driver changes for v3.16 Date: Thu, 10 Apr 2014 22:17:44 +0200 [thread overview] Message-ID: <CABxcv=miFY3gE6HOU5ovWwCzgC6Un3ANh_Weh_bPCb7OoYQ+pA@mail.gmail.com> (raw) In-Reply-To: <20140410193048.GE15736@drone.musicnaut.iki.fi> Hello Aaro, Thanks a lot for testing the series! On Thu, Apr 10, 2014 at 9:30 PM, Aaro Koskinen <aaro.koskinen@iki.fi> wrote: > Hi, > > On Thu, Apr 10, 2014 at 07:29:26PM +0200, Linus Walleij wrote: >> On Sun, Apr 6, 2014 at 4:58 PM, Javier Martinez Canillas >> <javier.martinez@collabora.co.uk> wrote: >> >> > Now that you have sent your changes for v3.15 to Torvalds, here are some >> > changes for the OMAP GPIO driver targeted to v3.16. Mostly improvements >> > so nothing here is -rc material. >> >> I like this series so I have applied them for v3.16, pending some ACK >> from Kevin &| Santosh. > > I tried these patches on OMAP1 on top of today's Torvalds git > (4ba85265790ba3681deeaf73f018c0eb829a7341). > > On Amstrad E3 I'm getting the following logs: > > [ 0.156491] omap_gpio omap_gpio.0: Runtime PM disabled, clock forced on. > [ 0.164604] genirq: Setting trigger mode 0 for irq 64 failed (gpio_irq_type+0x0/0x1f0) > [ 0.165418] genirq: Setting trigger mode 0 for irq 65 failed (gpio_irq_type+0x0/0x1f0) > [ 0.166133] genirq: Setting trigger mode 0 for irq 66 failed (gpio_irq_type+0x0/0x1f0) > [ 0.166838] genirq: Setting trigger mode 0 for irq 67 failed (gpio_irq_type+0x0/0x1f0) > [...] > [ 0.182856] genirq: Setting trigger mode 0 for irq 79 failed (gpio_irq_type+0x0/0x1f0) > [ 0.186887] omap_gpio omap_gpio.1: Could not get gpio dbck > [ 0.189308] genirq: Setting trigger mode 0 for irq 95 failed (gpio_irq_type+0x0/0x1f0) > [...] > [ 0.203121] genirq: Setting trigger mode 0 for irq 110 failed (gpio_irq_type+0x0/0x1f0) > > However it still seems to work. The serio is only GPIO IRQ and it > triggers when I press the external keyboard. > > The same happens also on Nokia 770: > > [ 0.118896] genirq: Setting trigger mode 0 for irq 128 failed (gpio_irq_type+0x0/0x220) > [ 0.119201] genirq: Setting trigger mode 0 for irq 129 failed (gpio_irq_type+0x0/0x220) > [...] > [ 0.124999] genirq: Setting trigger mode 0 for irq 143 failed (gpio_irq_type > +0x0/0x220) > [ 0.126831] omap_gpio omap_gpio.1: Could not get gpio dbck > [ 0.127258] OMAP GPIO hardware version 1.1 > [ 0.127624] omap_gpio omap_gpio.2: Could not get gpio dbck > [ 0.128204] omap_gpio omap_gpio.3: Could not get gpio dbck > [ 0.128753] omap_gpio omap_gpio.4: Could not get gpio dbck > > Here also GPIO IRQs (touchscreen, Retu) still work. > > A. I don't have those errors when booting on my DM3730 IGEPv2 board but it seems that for some reason on omap1 __irq_set_trigger() complains when IRQ_TYPE_NONE is used as a default flag when calling gpiochip_irqchip_add() Could you please test the following patch and tell me if your board still works and makes the errors go away? diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c index 8cc9e91..5bc8aec 100644 --- a/drivers/gpio/gpio-omap.c +++ b/drivers/gpio/gpio-omap.c @@ -1122,7 +1122,7 @@ static int omap_gpio_chip_init(struct gpio_bank *bank) ret = gpiochip_irqchip_add(&bank->chip, &gpio_irq_chip, irq_base, gpio_irq_handler, - IRQ_TYPE_NONE); + IRQ_TYPE_LEVEL_LOW); if (ret) { dev_err(bank->dev, "Couldn't add irqchip to gpiochip %d\n", ret); Best regards, Javier
WARNING: multiple messages have this Message-ID (diff)
From: javier@dowhile0.org (Javier Martinez Canillas) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/5] GPIO OMAP driver changes for v3.16 Date: Thu, 10 Apr 2014 22:17:44 +0200 [thread overview] Message-ID: <CABxcv=miFY3gE6HOU5ovWwCzgC6Un3ANh_Weh_bPCb7OoYQ+pA@mail.gmail.com> (raw) In-Reply-To: <20140410193048.GE15736@drone.musicnaut.iki.fi> Hello Aaro, Thanks a lot for testing the series! On Thu, Apr 10, 2014 at 9:30 PM, Aaro Koskinen <aaro.koskinen@iki.fi> wrote: > Hi, > > On Thu, Apr 10, 2014 at 07:29:26PM +0200, Linus Walleij wrote: >> On Sun, Apr 6, 2014 at 4:58 PM, Javier Martinez Canillas >> <javier.martinez@collabora.co.uk> wrote: >> >> > Now that you have sent your changes for v3.15 to Torvalds, here are some >> > changes for the OMAP GPIO driver targeted to v3.16. Mostly improvements >> > so nothing here is -rc material. >> >> I like this series so I have applied them for v3.16, pending some ACK >> from Kevin &| Santosh. > > I tried these patches on OMAP1 on top of today's Torvalds git > (4ba85265790ba3681deeaf73f018c0eb829a7341). > > On Amstrad E3 I'm getting the following logs: > > [ 0.156491] omap_gpio omap_gpio.0: Runtime PM disabled, clock forced on. > [ 0.164604] genirq: Setting trigger mode 0 for irq 64 failed (gpio_irq_type+0x0/0x1f0) > [ 0.165418] genirq: Setting trigger mode 0 for irq 65 failed (gpio_irq_type+0x0/0x1f0) > [ 0.166133] genirq: Setting trigger mode 0 for irq 66 failed (gpio_irq_type+0x0/0x1f0) > [ 0.166838] genirq: Setting trigger mode 0 for irq 67 failed (gpio_irq_type+0x0/0x1f0) > [...] > [ 0.182856] genirq: Setting trigger mode 0 for irq 79 failed (gpio_irq_type+0x0/0x1f0) > [ 0.186887] omap_gpio omap_gpio.1: Could not get gpio dbck > [ 0.189308] genirq: Setting trigger mode 0 for irq 95 failed (gpio_irq_type+0x0/0x1f0) > [...] > [ 0.203121] genirq: Setting trigger mode 0 for irq 110 failed (gpio_irq_type+0x0/0x1f0) > > However it still seems to work. The serio is only GPIO IRQ and it > triggers when I press the external keyboard. > > The same happens also on Nokia 770: > > [ 0.118896] genirq: Setting trigger mode 0 for irq 128 failed (gpio_irq_type+0x0/0x220) > [ 0.119201] genirq: Setting trigger mode 0 for irq 129 failed (gpio_irq_type+0x0/0x220) > [...] > [ 0.124999] genirq: Setting trigger mode 0 for irq 143 failed (gpio_irq_type > +0x0/0x220) > [ 0.126831] omap_gpio omap_gpio.1: Could not get gpio dbck > [ 0.127258] OMAP GPIO hardware version 1.1 > [ 0.127624] omap_gpio omap_gpio.2: Could not get gpio dbck > [ 0.128204] omap_gpio omap_gpio.3: Could not get gpio dbck > [ 0.128753] omap_gpio omap_gpio.4: Could not get gpio dbck > > Here also GPIO IRQs (touchscreen, Retu) still work. > > A. I don't have those errors when booting on my DM3730 IGEPv2 board but it seems that for some reason on omap1 __irq_set_trigger() complains when IRQ_TYPE_NONE is used as a default flag when calling gpiochip_irqchip_add() Could you please test the following patch and tell me if your board still works and makes the errors go away? diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c index 8cc9e91..5bc8aec 100644 --- a/drivers/gpio/gpio-omap.c +++ b/drivers/gpio/gpio-omap.c @@ -1122,7 +1122,7 @@ static int omap_gpio_chip_init(struct gpio_bank *bank) ret = gpiochip_irqchip_add(&bank->chip, &gpio_irq_chip, irq_base, gpio_irq_handler, - IRQ_TYPE_NONE); + IRQ_TYPE_LEVEL_LOW); if (ret) { dev_err(bank->dev, "Couldn't add irqchip to gpiochip %d\n", ret); Best regards, Javier
next prev parent reply other threads:[~2014-04-10 20:17 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-06 14:58 [PATCH 0/5] GPIO OMAP driver changes for v3.16 Javier Martinez Canillas 2014-04-06 14:58 ` Javier Martinez Canillas 2014-04-06 14:58 ` [PATCH 1/5] gpio: omap: convert to use irq_domain_add_simple() Javier Martinez Canillas 2014-04-06 14:58 ` Javier Martinez Canillas 2014-04-10 17:35 ` Santosh Shilimkar 2014-04-10 17:35 ` Santosh Shilimkar 2014-04-06 14:58 ` [PATCH 2/5] gpio: omap: check gpiochip_add() return value Javier Martinez Canillas 2014-04-06 14:58 ` Javier Martinez Canillas 2014-04-10 17:36 ` Santosh Shilimkar 2014-04-10 17:36 ` Santosh Shilimkar 2014-04-06 14:58 ` [PATCH 3/5] gpio: omap: add a GPIO_OMAP option instead of using ARCH_OMAP Javier Martinez Canillas 2014-04-06 14:58 ` Javier Martinez Canillas 2014-04-10 17:37 ` Santosh Shilimkar 2014-04-10 17:37 ` Santosh Shilimkar 2014-04-06 14:58 ` [PATCH 4/5] gpio: omap: convert driver to use gpiolib irqchip Javier Martinez Canillas 2014-04-06 14:58 ` Javier Martinez Canillas 2014-04-10 17:39 ` Santosh Shilimkar 2014-04-10 17:39 ` Santosh Shilimkar 2014-04-10 17:45 ` Linus Walleij 2014-04-10 17:45 ` Linus Walleij 2014-04-10 18:58 ` Javier Martinez Canillas 2014-04-10 18:58 ` Javier Martinez Canillas 2014-04-06 14:58 ` [PATCH 5/5] MAINTAINERS: update GPIO OMAP driver entry Javier Martinez Canillas 2014-04-06 14:58 ` Javier Martinez Canillas 2014-04-10 17:29 ` [PATCH 0/5] GPIO OMAP driver changes for v3.16 Linus Walleij 2014-04-10 17:29 ` Linus Walleij 2014-04-10 19:30 ` Aaro Koskinen 2014-04-10 19:30 ` Aaro Koskinen 2014-04-10 20:17 ` Javier Martinez Canillas [this message] 2014-04-10 20:17 ` Javier Martinez Canillas 2014-04-10 21:22 ` Aaro Koskinen 2014-04-10 21:22 ` Aaro Koskinen 2014-04-11 15:03 ` Javier Martinez Canillas 2014-04-11 15:03 ` Javier Martinez Canillas 2014-04-22 13:00 ` Linus Walleij 2014-04-22 13:00 ` Linus Walleij 2014-04-23 21:48 ` Javier Martinez Canillas 2014-04-23 21:48 ` Javier Martinez Canillas
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='CABxcv=miFY3gE6HOU5ovWwCzgC6Un3ANh_Weh_bPCb7OoYQ+pA@mail.gmail.com' \ --to=javier@dowhile0.org \ --cc=aaro.koskinen@iki.fi \ --cc=javier.martinez@collabora.co.uk \ --cc=khilman@linaro.org \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=nm@ti.com \ --cc=paul@pwsan.com \ --cc=santosh.shilimkar@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.