This is a note to let you know that I've just added the patch titled
wireless: cw1200: acquire hwbus lock around cw1200_irq_handler() call.
to the 3.11-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
wireless-cw1200-acquire-hwbus-lock-around-cw1200_irq_handler-call.patch
and it can be found in the queue-3.11 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 4978705d26149a629b9f50ff221caed6f1ae3048 Mon Sep 17 00:00:00 2001
From: Solomon Peachy <pizza@xxxxxxxxxxxx>
Date: Wed, 9 Oct 2013 12:15:11 -0400
Subject: wireless: cw1200: acquire hwbus lock around cw1200_irq_handler() call.
From: Solomon Peachy <pizza@xxxxxxxxxxxx>
commit 4978705d26149a629b9f50ff221caed6f1ae3048 upstream.
This fixes "lost interrupt" problems that occurred on SPI-based systems.
cw1200_irq_handler() expects the hwbus to be locked, but on the
SPI-path, that lock wasn't taken (unlike in the SDIO-path, where the
generic SDIO-code takes care of acquiring the lock).
Signed-off-by: David Mosberger <davidm@xxxxxxxxxx>
Signed-off-by: Solomon Peachy <pizza@xxxxxxxxxxxx>
Signed-off-by: John W. Linville <linville@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/net/wireless/cw1200/cw1200_spi.c | 2 ++
1 file changed, 2 insertions(+)
--- a/drivers/net/wireless/cw1200/cw1200_spi.c
+++ b/drivers/net/wireless/cw1200/cw1200_spi.c
@@ -237,7 +237,9 @@ static irqreturn_t cw1200_spi_irq_handle
struct hwbus_priv *self = dev_id;
if (self->core) {
+ cw1200_spi_lock(self);
cw1200_irq_handler(self->core);
+ cw1200_spi_unlock(self);
return IRQ_HANDLED;
} else {
return IRQ_NONE;
Patches currently in stable-queue which might be from pizza@xxxxxxxxxxxx are
queue-3.11/wireless-cw1200-acquire-hwbus-lock-around-cw1200_irq_handler-call.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html