[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150918.093556.101988084572410337.okuno.kohji@jp.panasonic.com>
Date: Fri, 18 Sep 2015 09:35:56 +0900
From: Kohji Okuno <okuno.kohji@...panasonic.com>
To: <tglx@...utronix.de>
CC: <linux-kernel@...r.kernel.org>, <okuno.kohji@...panasonic.com>
Subject: Re: [PATCH] genirq: Fix bad IRQ_ONSHOT in forced IRQ setting
From: Thomas Gleixner <tglx@...utronix.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.
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