summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/hostap/hostap_main.c
diff options
context:
space:
mode:
authorSolomon Peachy <pizza@shaftnet.org>2013-08-28 04:29:46 +0400
committerJohn W. Linville <linville@tuxdriver.com>2013-09-09 22:40:53 +0400
commitaec8e88c947b7017e2b4bbcb68a4bfc4a1f8ad35 (patch)
tree584e2a99402483e16d6145bdf1d29416a1a0abce /drivers/net/wireless/hostap/hostap_main.c
parente7d33bb5ea82922e6ddcfc6b28a630b1a4ced071 (diff)
downloadlinux-aec8e88c947b7017e2b4bbcb68a4bfc4a1f8ad35.tar.xz
cw1200: Don't perform SPI transfers in interrupt context
When we get an interrupt from the hardware, the first thing the driver does is tell the device to mask off the interrupt line. Unfortunately this involves a SPI transaction in interrupt context. Some (most?) SPI controllers perform the transfer asynchronously and try to sleep. This is bad, and triggers a BUG(). So, work around this by using adding a hwbus hook for the cw1200 driver core to call. The cw1200_spi driver translates this into irq_disable()/irq_enable() calls instead, which can safely be called in interrupt context. Apparently the platforms I used to develop the cw1200_spi driver used synchronous spi_sync() implementations, which is why this didn't surface until now. Many thanks to Dave Sizeburns for the inital bug report and his services as a tester. Signed-off-by: Solomon Peachy <pizza@shaftnet.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/hostap/hostap_main.c')
0 files changed, 0 insertions, 0 deletions