Hi, > Patch attached. We are in a chicken and egg situation. The controller > needs data to cause the clock to start and the first command sent by the > mmc layer is CMD0 -- mmc_go_idle(). This is sent without the eMMC chip > seeing the 74 clocks but since there are NOW clocks the chip see's this. > It is not able to parse the command and we are struck.
Okay, and some host->ops->generate_initial_74_clocks() could help you out, it seems. If it is a controller specific issue, the approach seems in general sensible to me, unless I am missing some details. Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ |
signature.asc
Description: Digital signature
