On Thu, May 8, 2014 at 7:17 AM, Dong Aisheng <b29396@xxxxxxxxxxxxx> wrote: > I'm not very sure about HYS bit, but it should not be pad setting issue. > This pad setting was tested ok with FSL internal tree. > > I just tested an old Chris/mmc-next tree which is 3.14 rc2 with the top commit is b42b9b. > The eMMC works well on SabreSD boards. > But it failed and got the same issue with latest chris/mmc-next tree. > I noticed there's no changes on sdhci-esdhc-imx.c > Probably some other changes breaks this function. > > Fabio, > You may bisect it yourself or i will do it later when i'm a bit free. Ok, I have just tested with Shawn's branch and the mmc error does not happen, so it must be something in linux-next that causes the issue. Will submit the dts change. Regards, Fabio Estevam -- 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
