On Mon, Jun 10, 2013 at 5:03 PM, Ulf Hansson <ulf.hansson@xxxxxxxxxxxxxx> wrote: > From: Ulf Hansson <ulf.hansson@xxxxxxxxxx> > > The MMC/SD/SDIO cards are registered on the mmc_bus and should from a power > management perspective be controlled from there. As of today each and every > host driver needs to issue mmc_suspend|resume_host from their respective > .suspend|resume methods, which seems like an unnecessary requirement to > put on them. Additionally, a shutdown sequence shall be initiated from the > mmc_bus. > > This patch set moves the responsiblity to suspend the cards into the mmc_bus. > It also invents the shutdown sequence, also to be handled from the mmc_bus. > In the SDIO case, the shutdown sequence will not involve any SDIO specific > operations. If this would be desired, I suggest to handle that as and separate > step, since it would involve the sdio bus and potentially the sdio drivers. > > As a part of the patches releated to adding the shutdown sequence, specific > issues to handle eMMC power off notification properly are included in this > patch set as well. > > The mmc_suspend|resume_host functions are not removed, but will instead always > return successful. A separate patch(es) build on top of this patch set, shall > remove the API:s together with updating each and every host driver. > > Do note, that patch 1 to 4 has been sent earlier in the set "mmc: core: Let the > mmc_bus handle suspend|resume sequence". Since the functionallity are very close > releated I decided to fold them in into this patch set. > > A big thank you to Jaehoon Chung who has tested the patches 1 to 4. Hm a significant portion of this patch set hits code which has not been touched since Pierre Ossman wrote the first MMC code. E.g. patch 1. I know Pierre has long since moved on to other things, but I'm pinging him anyway since it's his code after all... Pierre: tell us if you want a copy of this patch set. Yours, Linus Walleij -- 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
