Sergei Shtylyov 883f7c326f 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> Cc: stable@vger.kernel.org Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2019-03-19 13:14:11 +01:00
..
card	mmc: mmc_test: Uninitialized return value	2017-01-12 11:39:31 +01:00
core	mmc: core: Use a minimum 1600ms timeout when enabling CACHE ctrl	2018-12-29 13:40:15 +01:00
host	mmc: tmio_mmc_core: don't claim spurious interrupts	2019-03-19 13:14:11 +01:00
Kconfig	…
Makefile	…