On gio, dic 17, 2015 at 02:00:17 +0000, Yang, York wrote: > Hi, Carlo Hi Yang, > I don't understand. We can see that 9faac7b95 is all about > DDR50. It should not affect the behavior of SDR50. What I'm saying is that this commit is negatively affecting some DDR50 SDIO card as in my case. Ok, let's try to go through the code with and without 9faac7b95. Without 9faac7b95: - mmc_sdio_init_uhs_card() is called - sw_caps.sd3_bus_mode is 0x14 (SD_MODE_UHS_SDR50 | SD_MODE_UHS_DDR50) - card->sw_caps.sd3_bus_mode & SD_MODE_UHS_SDR50 is verified and mmc_execute_tuning() is called - sdhci_execute_tuning() is called - host->timing is MMC_TIMING_UHS_DDR50 - since there is no case for that we end up in 'default', goto out_unlock and CMD19 is never issued With 9faac7b95: - mmc_sdio_init_uhs_card() is called - sw_caps.sd3_bus_mode is 0x14 (SD_MODE_UHS_SDR50 | SD_MODE_UHS_DDR50) - card->sw_caps.sd3_bus_mode & SD_MODE_UHS_SDR50 is verified and mmc_execute_tuning() is called - sdhci_execute_tuning() is called - host->timing is MMC_TIMING_UHS_DDR50 - this time we have the the 'case MMC_TIMING_UHS_DDR50' and we break on that - CMD19 is issued and the card stops working > Since the commit is very simple, you may remove the change one by one > by yourself. And see if any difference occurs. As stated above the problem is in the new 'case MMC_TIMING_UHS_DDR50' we have in sdhci_execute_tuning() > Besides, please check > if the card->sw_caps.sd3_bus_mode changes with or without DDR50 tuning > enabled. It doesn't. -- 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
