From: Thomas Gleixner <tglx@linutronix.de>
To: Kohji Okuno <okuno.kohji@jp.panasonic.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH] genirq: Fix bad IRQ_ONSHOT in forced IRQ setting
Date: Fri, 18 Sep 2015 11:04:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509180955290.3951@nanos> (raw)
In-Reply-To: <20150918.093556.101988084572410337.okuno.kohji@jp.panasonic.com>
On Fri, 18 Sep 2015, Kohji Okuno wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Thu, 17 Sep 2015 23:10:02 +0200
> > On Thu, 17 Sep 2015, Kohji Okuno wrote:
> >>
> >> When 1st sdio IRQ is happend, sdhci_irq() returns IRQ_WAKE_THREAD.
> >> After this, sdhci_irq() is not called in case of threadirqs.
> >
> > What kind of system is that?
> >
> > Can you provide the output of /proc/interrupts please?
> >
> > I think your patch is fine. I just want to understand why we don't see
> > any more interrupts.
> >
> > Thanks,
> >
> > tglx
>
> Hi tglx,
>
> My system is arm, and I connect SDIO WiFi card.
> In fact, I use kernel 3.18.11 base. But, I think sources concerned
> with this are same.
>
> This is my "/proc/interrupts".
>
> CPU0 CPU1 CPU2 CPU3
> 46: 20672 0 0 0 GIC 46 mmc1
>
> In drivers/irqchip/irq-gic.c:gic_set_type(), irq46 is set as
> IRQ_TYPE_LEVEL_HIGH.
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.
Thanks,
tglx
next prev parent reply other threads:[~2015-09-18 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 7:13 Kohji Okuno
2015-09-17 7:59 ` Thomas Gleixner
2015-09-17 8:21 ` Kohji Okuno
2015-09-17 9:48 ` Kohji Okuno
2015-09-17 21:10 ` Thomas Gleixner
2015-09-18 0:35 ` Kohji Okuno
2015-09-18 9:04 ` Thomas Gleixner [this message]
2015-09-18 9:22 ` Kohji Okuno
2015-09-18 10:03 ` Marc Zyngier
2015-09-18 10:56 ` Kohji Okuno
2015-09-18 14:46 ` Thomas Gleixner
2015-09-19 15:33 ` Kohji Okuno
2015-09-19 20:24 ` Thomas Gleixner
2015-09-20 0:21 ` Kohji Okuno
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=alpine.DEB.2.11.1509180955290.3951@nanos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=okuno.kohji@jp.panasonic.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
all inboxes | Powered by JetHome®