Changes in v3: - Added Tested/Reviewed-by tags from Dough. (Dough, I used your chromium.org email, please tell if you want me to change). - Updated change logs. - Some other minor changes, described in each patch history. Changes in v2: - Folded in a new change, patch 1/5 to fix a race condition while processing SDIO IRQs. - Fixed review comments provided by Dough. - Updated change logs. - Small changes to how ->ack_sdio_irq() is being invoked, to simplify code. - Added a revert patch of the dw_mmc change for runtime PM issues, which was a quick fix for stable/fixes. Regressions for SDIO IRQs have been reported for dw_mmc, caused by enabling runtime PM support for it. This series extends and improves the SDIO IRQs support in the core, such that it also better suites the need for dw_mmc, particulary around runtime PM. To accomplish this a new method to process and signal SDIO IRQs are invented, based on a work/workqueue, but built upon the existing support for MMC_CAP2_SDIO_IRQ_NOTHREAD. Next steps after this series is to convert the SDIO IRQ polling mechanism from using the kthread to also use the work/workqueue method. Additonally we should also try to migrate all host drivers supporting SDIO IRQ to use the new method instead, which in the end would enable us to remove the old mmc_signal_sdio_irq() API along with the ktread. Ulf Hansson (5): mmc: core: Prevent processing SDIO IRQs when none is claimed mmc: sdio: Add API to manage SDIO IRQs from a workqueue mmc: dw_mmc: Convert to use MMC_CAP2_SDIO_IRQ_NOTHREAD for SDIO IRQs mmc: dw_mmc: Prevent runtime PM suspend when SDIO IRQs are enabled Revert "mmc: dw_mmc: Don't allow Runtime PM for SDIO cards" drivers/mmc/core/host.c | 2 ++ drivers/mmc/core/sdio_irq.c | 22 ++++++++++++++++++++-- drivers/mmc/core/sdio_ops.h | 2 ++ drivers/mmc/host/dw_mmc.c | 42 +++++++++++++++++++++++++++++++----------- include/linux/mmc/host.h | 3 +++ 5 files changed, 58 insertions(+), 13 deletions(-) -- 2.7.4 -- 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
