From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
linux-omap@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [BISECTED] v4.4-rc1 GPIO regression on OMAP1
Date: Thu, 19 Nov 2015 13:57:37 +0200 [thread overview]
Message-ID: <564DB931.8090904@ti.com> (raw)
In-Reply-To: <20151118183106.GC18138@blackmetal.musicnaut.iki.fi>
On 11/18/2015 08:31 PM, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Nov 18, 2015 at 02:58:38PM +0200, Grygorii Strashko wrote:
>> On 11/17/2015 11:42 PM, Aaro Koskinen wrote:
>>> Amstrad E3 computer (OMAP1) boot crashes early with v4.4-rc1. Bisected to:
>>>
>>> 450fa54cfd66e3dda6eda26256637ee8928af12a is the first bad commit
>>> commit 450fa54cfd66e3dda6eda26256637ee8928af12a
>>> Author: Grygorii Strashko <grygorii.strashko@ti.com>
>>> Date: Fri Sep 25 12:28:03 2015 -0700
>>>
>>> gpio: omap: convert to use generic irq handler
>>
>> Could you check pls if below change will solve this issue, pls?
>>
>> iff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
>> index 56d2d02..2905e0d 100644
>> --- a/drivers/gpio/gpio-omap.c
>> +++ b/drivers/gpio/gpio-omap.c
>> @@ -1129,7 +1129,7 @@ static int omap_gpio_chip_init(struct gpio_bank *bank,
>> struct irq_chip *irqc)
>> }
>>
>> ret = gpiochip_irqchip_add(&bank->chip, irqc,
>> - irq_base, handle_bad_irq,
>> + irq_base, handle_simple_irq,
>> IRQ_TYPE_NONE);
>
Thanks for testing it. But I'd like to ask you for more help here if possible :)
Above change is expected to fix the OMAP1 boot, but looking at the OMAP GPIO code
I think that MPUIO IRQ are not working :( and this functionality has been broken
long time ago - commit "gpio: omap: convert to use generic irq handler" has just
made hidden issue visible.
(I've found only one OMAP1 board which uses MPUIO GPIO as IRQ (board-osk.c)).
So, could I ask you to test another change instead of previous one?
--- a/drivers/gpio/gpio-omap.c
+++ b/drivers/gpio/gpio-omap.c
@@ -1122,8 +1122,6 @@ static int omap_gpio_chip_init(struct gpio_bank *bank, struct irq_chip *irqc)
/* MPUIO is a bit different, reading IRQ status clears it */
if (bank->is_mpuio) {
irqc->irq_ack = dummy_irq_chip.irq_ack;
- irqc->irq_mask = irq_gc_mask_set_bit;
- irqc->irq_unmask = irq_gc_mask_clr_bit;
if (!bank->regs->wkup_en)
irqc->irq_set_wake = NULL;
}
In my opinion real test will be
- request(any MPUIO GPIO IRQ, IRQF_TRIGGER_LOW/HIGH),
- trigger MPUIO GPIO IRQ
- free(MPUIO GPIO IRQ)
--
regards,
-grygorii
next prev parent reply other threads:[~2015-11-19 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 21:42 [BISECTED] v4.4-rc1 GPIO regression on OMAP1 Aaro Koskinen
2015-11-18 12:58 ` Grygorii Strashko
2015-11-18 18:31 ` Aaro Koskinen
2015-11-19 11:57 ` Grygorii Strashko [this message]
2015-11-19 21:02 ` Aaro Koskinen
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=564DB931.8090904@ti.com \
--to=grygorii.strashko@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=javier@dowhile0.org \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).