| commit | 0d7755e450865b76b98e3fea2e166b0a2266972d | |
| author | Nicolas Pitre <nicolas.pitre@linaro.org> | |
| Mon, 16 Apr 2012 23:16:54 +0000 (16 19:16 -0400) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Fri, 1 Jun 2012 07:13:00 +0000 (1 15:13 +0800) | ||
| tree | f8cd534b07f01aaf1e990ab3ca336c1f75adb46c | treesnapshot (tar.gz zip) |
| parent | 1c4f53ca32463a742583976f40444ce4485f3cf9 | commitdiff |
mmc: sdio: avoid spurious calls to interrupt handlers
commit bbbc4c4d8c5face097d695f9bf3a39647ba6b7e7 upstream.
Commit 06e8935feb ("optimized SDIO IRQ handling for single irq")
introduced some spurious calls to SDIO function interrupt handlers,
such as when the SDIO IRQ thread is started, or the safety check
performed upon a system resume. Let's add a flag to perform the
optimization only when a real interrupt is signaled by the host
driver and we know there is no point confirming it.
Reported-by: Sujit Reddy Thumma <sthumma@codeaurora.org>
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Signed-off-by: Chris Ball <cjb@laptop.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit bbbc4c4d8c5face097d695f9bf3a39647ba6b7e7 upstream.
Commit 06e8935feb ("optimized SDIO IRQ handling for single irq")
introduced some spurious calls to SDIO function interrupt handlers,
such as when the SDIO IRQ thread is started, or the safety check
performed upon a system resume. Let's add a flag to perform the
optimization only when a real interrupt is signaled by the host
driver and we know there is no point confirming it.
Reported-by: Sujit Reddy Thumma <sthumma@codeaurora.org>
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Signed-off-by: Chris Ball <cjb@laptop.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| drivers/mmc/core/sdio.c | diffblobblamehistory | |
| drivers/mmc/core/sdio_irq.c | diffblobblamehistory | |
| include/linux/mmc/host.h | diffblobblamehistory |