diff options
author | Ni Wade <wni@nvidia.com> | 2012-08-27 10:25:10 +0000 |
---|---|---|
committer | John Weber <rjohnweber@gmail.com> | 2013-07-28 23:45:11 -0500 |
commit | c01ebb6ca08326a7d2309efc68329f4147c6d5e5 (patch) | |
tree | 3ecbc7237a027cfbee23902dd390a362c2cf2ea8 /init | |
parent | 29c8561c8d6d248f2b6726384815a136c2fbd859 (diff) | |
download | linux-c01ebb6ca08326a7d2309efc68329f4147c6d5e5.tar.gz |
brcmfmac: Handling the interrupt in ISR directly for non-OOB
In case of inband interrupts, if we handle the interrupt in dpc thread,
two level of thread switching takes place to process wifi interrupts.
One in SDHCI driver and the other in Wifi driver. This may cause the system
instability.
Because the SDHCI calls sdio_irq_thread() to handle the irq, this thread locks
mmc host and calls wifi handler. It expects WiFi handler to be quick and
enables sdio interrupt from card at end. If wifi handler defers this work for
a different thread, sdio_irq_thread() will be stuck on next wifi interrupt
since mmc lock is not freed.
Handling the interrupt in ISR directly will prevent thread context switching in
wifi driver. It can fix the instability problems.
Signed-off-by: Wei Ni <wni@nvidia.com>
(cherry picked from commit c782ec69711573ee082fa78b80dae3897269266e)
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions