Hi Ulf, On Fri, May 9, 2014 at 5:42 AM, Ulf Hansson <[email protected]> wrote: > On 9 May 2014 08:53, Dong Aisheng <[email protected]> wrote: >> The regression is caused by the following commit ... >> >> commit 79f7ae7c45a6ccf04e2908337461dee615f6afb0 >> Author: Seungwon Jeon <[email protected]> >> Date: Fri Mar 14 21:11:56 2014 +0900 >> >> mmc: clarify DDR timing mode between SD-UHS and eMMC >> >> This change distinguishes DDR timing mode of current >> mixed usage to clarify device type. >> >> Signed-off-by: Seungwon Jeon <[email protected]> >> Acked-by: Jaehoon Chung <[email protected]> >> Signed-off-by: Ulf Hansson <[email protected]> >> Signed-off-by: Chris Ball <[email protected]> >> >> ... and the line below. >> >> @@ -1264,7 +1264,7 @@ static int mmc_init_card(struct mmc_host *host, u32 >> ocr, >> goto err; >> } >> mmc_card_set_ddr_mode(card); >> - mmc_set_timing(card->host, MMC_TIMING_UHS_DDR50); >> + mmc_set_timing(card->host, MMC_TIMING_MMC_DDR52); >> mmc_set_bus_width(card->host, bus_width); >> } >> } >> >> It's caused by the platform driver was still using MMC_TIMING_UHS_DDR50 for >> MMC DDR >> mode which needs update too. >> >> Reported-by: Fabio Estevam <[email protected]> >> Reported-by: Shawn Guo <[email protected]> >> Signed-off-by: Dong Aisheng <[email protected]> > > Hi Dong, > > Thanks for the fix. I will include this in the next PR I send to Chris.
It seems this one is still missing in linux-next. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
