[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150918.182207.856288392397747867.okuno.kohji@jp.panasonic.com>
Date: Fri, 18 Sep 2015 18:22:07 +0900
From: Kohji Okuno <okuno.kohji@...panasonic.com>
To: <tglx@...utronix.de>
CC: <linux-kernel@...r.kernel.org>, <marc.zyngier@....com>,
<okuno.kohji@...panasonic.com>
Subject: Re: [PATCH] genirq: Fix bad IRQ_ONSHOT in forced IRQ setting
From: Thomas Gleixner <tglx@...utronix.de>
Date: Fri, 18 Sep 2015 11:04:23 +0200
> That's weird. The flow is:
>
> interrupt()
> mask()
> ret = primary_handler()
> if (ret == WAKE_THREAD)
> wake_thread()
> else
> unmask()
>
> thread_handler()
> ....
> unmask()
>
> So if an interrupt is triggered on the device while the interrupt is
> masked it should be raised again immediately when the unmask happens
> because its level type.
>
> I'm wondering why that doesn't work.
Yes. I think so. And, I have just found that sdhci_thread_irq() don't
finish in this case. I'm analyzing about this now. But, after I apply
my patch, sdhci_thread_irq() can finish. I will share the result with
you.
Best regards,
Kohji Okuno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists