2009/11/23 Ladislav Michl <Ladislav.Michl@xxxxxxxxx>: > And sorry to ask again. This very driver works reliable and there are no > timeouts like this > mmci-omap mmci-omap.0: command timeout (CMD8) > mmci-omap mmci-omap.0: command timeout (CMD5) > mmci-omap mmci-omap.0: command timeout (CMD5) > mmci-omap mmci-omap.0: command timeout (CMD5) > mmci-omap mmci-omap.0: command timeout (CMD5) > mmci-omap mmci-omap.0: command timeout (CMD55) > mmci-omap mmci-omap.0: command timeout (CMD55) > mmci-omap mmci-omap.0: command timeout (CMD55) > mmci-omap mmci-omap.0: command timeout (CMD55) > while detecting MMC card on OMAP730? (because I can see them on 5910). This question > is unrelated to your patch. > Yes, this driver (after patching) works reliably on OMAP7XX. The CMD5/8 timeouts seem normal and non-fatal. CMD55 is the "init" command that has to work. We had an old problem causing output just like what you report - it turned out we missed a GPIO to power up the MMC card. -- Alistair Buxton a.j.buxton@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
