Reference in a new issue

Blame

Copy permalink

Reference in a new issue

Copy permalink

Sergei Shtylyov 011870d83a mmc: tmio_mmc_core: don't claim spurious interrupts ... commit 5c27ff5db1 upstream. I have encountered an interrupt storm during the eMMC chip probing (and the chip finally didn't get detected). It turned out that U-Boot left the DMAC interrupts enabled while the Linux driver didn't use those. The SDHI driver's interrupt handler somehow assumes that, even if an SDIO interrupt didn't happen, it should return IRQ_HANDLED. I think that if none of the enabled interrupts happened and got handled, we should return IRQ_NONE -- that way the kernel IRQ code recoginizes a spurious interrupt and masks it off pretty quickly... Fixes: 7729c7a232 ("mmc: tmio: Provide separate interrupt handlers") Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Reviewed-by: Simon Horman <horms+renesas@verge.net.au> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> [bwh: Backported to 3.16: - tmio_mmc_sdio_irq() can be used directly as an interrupt handler, so make it return IRQ_NONE for unhandled interrupts - Adjust filename] Signed-off-by: Ben Hutchings <ben@decadent.org.uk>		History 2019-05-02 21:41:59 +01:00
..
card	mmc: core: use mrq->sbc when sending CMD23 for RPMB	2019-02-11 17:54:18 +00:00
core	mmc: core: Use a minimum 1600ms timeout when enabling CACHE ctrl	2019-02-11 17:54:27 +00:00
host	mmc: tmio_mmc_core: don't claim spurious interrupts	2019-05-02 21:41:59 +01:00
Kconfig	mmc: explicitly mention SDIO support in Kconfig	2008-10-12 11:04:36 +02:00
Makefile	mmc: sdhci-pci: add platform data	2012-01-11 23:58:47 -05:00