summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2014-02-15 00:55:19 (GMT)
committerThomas Gleixner <tglx@linutronix.de>2014-02-19 16:22:44 (GMT)
commita92444c6b2225a9115d661c950cb48a22aeace20 (patch)
treead76dd71c9fec1648469009cb356351ca23daef0 /fs
parent18258f7239a61d8929b8e0c7b6d46c446459074c (diff)
downloadlinux-a92444c6b2225a9115d661c950cb48a22aeace20.tar.xz
genirq: Provide irq_wake_thread()
In course of the sdhci/sdio discussion with Russell about killing the sdio kthread hackery we discovered the need to be able to wake an interrupt thread from software. The rationale for this is, that sdio hardware can lack proper interrupt support for certain features. So the driver needs to poll the status registers, but at the same time it needs to be woken up by an hardware interrupt. To be able to get rid of the home brewn kthread construct of sdio we need a way to wake an irq thread independent of an actual hardware interrupt. Provide an irq_wake_thread() function which wakes up the thread which is associated to a given dev_id. This allows sdio to invoke the irq thread from the hardware irq handler via the IRQ_WAKE_THREAD return value and provides a possibility to wake it via a timer for the polling scenarios. That allows to simplify the sdio logic significantly. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Russell King <linux@arm.linux.org.uk> Cc: Chris Ball <chris@printf.net> Acked-by: Peter Zijlstra <peterz@infradead.org> Link: http://lkml.kernel.org/r/20140215003823.772565780@linutronix.de
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions