diff options
author | Stanislaw Gruszka <sgruszka@redhat.com> | 2012-01-13 12:59:32 +0100 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2012-01-13 14:40:57 -0500 |
commit | dfd00c4c8f3dfa1fd7cec45f83d98b2a49743dcd (patch) | |
tree | 918140b949cc6189294d27f688925cc3a763ed63 /net | |
parent | 92c1ff1fa772ee76a18ae1edd2e4baecf381f17e (diff) | |
download | linux-stable-dfd00c4c8f3dfa1fd7cec45f83d98b2a49743dcd.tar.gz linux-stable-dfd00c4c8f3dfa1fd7cec45f83d98b2a49743dcd.tar.bz2 linux-stable-dfd00c4c8f3dfa1fd7cec45f83d98b2a49743dcd.zip |
rt2800pci: fix spurious interrupts generation
Same devices can generate interrupt without properly setting bit in
INT_SOURCE_CSR register (spurious interrupt), what will cause IRQ line
will be disabled by interrupts controller driver.
We discovered that clearing INT_MASK_CSR stops such behaviour. We
previously first read that register, and then clear all know interrupt
sources bits and do not touch reserved bits. After this patch, we write
to all register content (I believe writing to reserved bits on that
register will not cause any problems, I tested that on my rt2800pci
device).
This fix very bad performance problem, practically making device
unusable (since worked without interrupts), reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=658451
We previously tried to workaround that issue in commit
4ba7d9997869d25bd223dea7536fc1ce9fab3b3b "rt2800pci: handle spurious
interrupts", but it was reverted in commit
82e5fc2a34fa9ffea38f00c4066b7e600a0ca5e6
as thing, that will prevent to detect real spurious interrupts.
Reported-and-tested-by: Amir Hedayaty <hedayaty@gmail.com>
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions