On Wed, Nov 30, 2011 at 5:00 PM, Joe Woodward <jw@xxxxxxxxxxxxxx> wrote: > It seems CMD5 fails (which seems to be what the workarounds were aiming to fix). Right; you get a timeout (-110), which means the 8686 didn't send any response. This is unexpected because the sdio reset (the CMD52 you see before the init sequence) should be enough to reset the device (we confirmed this with the Marvell folks on this list awhile ago). > I'm afraid I may not be of much more use as Gumstix (annoyingly) don't release schematics of their COMs, so actually probing any signals isn't really possible. Yes, it makes it difficult to debug. You can try to verify (in the code) that all the text book prerequisites are there (e.g. all SDIO lines are pulled up and muxed correctly. though since stuff work for you without SDIO runtime PM, I assume these are ok), and maybe even play a bit with stuff like delays, sdio resets and power cycles and see if things change. If you have access to the other inputs of the 8686 (it has several of them which are related to power and resets. Neither me nor Daniel have intimate knowledge about what any of those really do, but you could dig some info from emails send by Marvell folks on this list), then you can also try to play with them and see if things change. With luck, you could learn more about the problem and can hopefully get closer to finding a solution. It could be great if a solution will be found, but if not, we'll probably have to proceed with the revert... Good luck! Ohad. -- 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
