Hi, Since it's introduction, our MMC controller has had its external clocks running all the time. While that was working great, the power usage and most importantly the EMI that it generated was pretty bad. Let's implement some runtime_pm hooks with an autosuspend to shut down the whole block when the MMC is not active. However, some SDIO devices will not probe properly if we keep shutting down the controller, so the autosuspend is disabled for the SDIO devices. Let me know what you think, Maxime Changes from v1: - Disable entirely the controller - Made sure the driver would work with CONFIG_PM off - Fixed an issue with the SDIO devices - Rebased on top of 4.16 Maxime Ripard (8): mmc: sunxi: Reorder the headers mmc: sunxi: Move the power off action in a separate function mmc: sunxi: Move the power on action in a separate function mmc: sunxi: Move the power up action in a separate function mmc: sunxi: Move resources management to separate functions mmc: sunxi: Move the reset deassertion before enabling the clocks mmc: sunxi: Set our device drvdata earlier mmc: sunxi: Add runtime_pm support drivers/mmc/host/sunxi-mmc.c | 346 ++++++++++++++++++++++-------------- 1 file changed, 216 insertions(+), 130 deletions(-) base-commit: 661e50bc853209e41a5c14a290ca4decc43cbfd1 -- git-series 0.9.1 -- 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
