On Sat, Feb 15, 2014 at 12:55:19AM -0000, Thomas Gleixner wrote: > 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@xxxxxxxxxxxxx> Acked-by: Peter Zijlstra <peterz@xxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
