On Sun, Jan 2, 2011 at 11:23 PM, Philip Rakity <prakity@xxxxxxxxxxx> wrote: > > why not just not compile the the code without clock gating defined ? > > and if code cannot run with it clock gating defined do a > #error ? The problem here is not related to the drivers that wont compile with clock gating. sdio clock gating, is that you gate the sdio bus clock when you dont need it. Because some vendors sdio card IP is bad, some card are not working properly when you do this (Their interrupt logic might need a clock to trigger interrupt, or they are derivating their own internal clock from the sdio bus clock). Those card are wrong thus I'm using a quirk to deal with them. The problem is that we still dont know how many card are wrong and what are they. So that's why I'm making it default for all sdio card at the moment. When we'll have more experience on this, we can switch the behaviour, and make it a default off. > Also from the diff I think you patch changes the behavior of SD/eMMC cards which may not be what you want . The quirk is only set for sdio cards, which is, I think, equivalent to the previous implementation. - if (mmc_card_sdio(card)) - return false; - - return true; + return !(card->quirks & MMC_QUIRK_BROKEN_CLK_GATING); @@ -785,6 +785,12 @@ int mmc_attach_sdio(struct mmc_host *host, u32 ocr) + card->quirks |= MMC_QUIRK_BROKEN_CLK_GATING; This code is made to propose a solution for allowing drivers owner that *knows* that their card work with CG, to disable the quirk in their probe function. Pierre -- 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
