On Sat, Jun 13, 2009 at 3:40 AM, Madhusudhan<madhu.cr@xxxxxx> wrote:
<snip>
> Hugo,
>
> Your CLK and CMD line mux does not look correct to me.
>
> Try the below settings.
>
> MUX_CFG_34XX("AF10_3430_MMC3_CLK", 0x5d8,
> OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
> MUX_CFG_34XX("AC3_3430_MMC3_CMD", 0x1d0,
> OMAP34XX_MUX_MODE3 | OMAP34XX_PIN_INPUT_PULLUP)
>
> CMD1 can never go through if your MUX is wrong.
>
> Let me know if this helps.
>
> Regards,
> Madhu
Thanks Madhu. Your updated settings seem wrong to me (at least for the
way my particular board is wired). Perhaps there is a difference
between the 3430 and 3503 in this respect (I don't have the 3430
datasheet so can't check). Note I'm using MMC3_CLK and CMD that are
muxed on balls AF10 and AE10. It's a shame Gumstix chose not to
publish the Overo modules' schematics - having them would have made
this problem much easier to debug!
After some experimentation, the following mux settings are working
with my hardware:
+/* MMC3 */
+MUX_CFG_34XX("AF10_3430_MMC3_CLK", 0x5d8,
+ OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
+MUX_CFG_34XX("AE10_3430_MMC3_CMD", 0x5da,
+ OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
+MUX_CFG_34XX("AE11_3430_MMC3_DAT0", 0x5e4,
+ OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
+MUX_CFG_34XX("AH9_3430_MMC3_DAT1", 0x5e6,
+ OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
+MUX_CFG_34XX("AF13_3430_MMC3_DAT2", 0x5e8,
+ OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
+MUX_CFG_34XX("AE13_3430_MMC3_DAT3", 0x5e2,
+ OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
For the archive, it looks like the ehci driver (which has some hackish
out-of-tree patches specific to the Overo) was messing up my padconf
settings even though they were correct in u-boot. The other
possibility, is that u-boot wasn't defining the CLK signal with input
enable; this gives the following mux debug message:
MUX: setup AF10_3430_MMC3_CLK (0xd80025d8): 0x001a -> 0x011a
Thanks everyone for your help!
Hugo
--
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
