On Wed, Sep 23, 2015 at 9:25 PM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > [...] > >>> >>> Also, I was giving this a second thought... >>> >>> What happens with the SD 3.0 card when it *doesn't* support CMD19. >>> Will it still be functional afterwards or will it move from "transfer >>> state" to another not known state? >> >> uffe, i am not the expert of this issue but weijun is. weijun told that >> for the cards who don't support cmd19, it will take it as illegal >> command and not response it. and it also sets illegal command error in >> registers. >> but the card status is still functional and doesn't cause unknown state. >> >> so maybe we can just ignore the err of tuning, and use the second >> patch with the refine you mentioned? > > Sure, let's do that. Please send a v2 of the patchset then. Replying here since I'm not subscribed to linux-mmc. Commit 9faac7b95 "mmc: sdhci: enable tuning for DDR50" actually breaks WiFi on SDIO at least for the ASUS X205TA. I tried to ignore the error from the tuning also for the SDIO card patching mmc_sdio_init_uhs_card() in drivers/mmc/core/sdio.c but I end up with the error "Controller never released inhibit bit(s)". At least in my case CMD19 shouldn't be issued at all to have the SDIO card working. Any suggestion how to approach this problem? -- Carlo Caione -- 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
