On Wed, Aug 5, 2009 at 12:25 PM, Kevin Hilman<[email protected]> wrote: > John Sarman <[email protected]> writes: > >> ---------- Forwarded message ---------- >> From: John Sarman <[email protected]> >> Date: Wed, Aug 5, 2009 at 12:01 PM >> Subject: Re: MMC3 Overo >> To: Grazvydas Ignotas <[email protected]> >> >> >> On Wed, Aug 5, 2009 at 4:32 AM, Grazvydas Ignotas<[email protected]> wrote: >>>> <u-boot_snip> >>>> MUX_VAL(CP(ETK_CLK_ES2), (IDIS | PTU | EN | M2)) /*MMC3_CLK*/\ >>> >>> You must have input enable on CLK line for MMC3 or it won't work for >>> some reason (MMC 1 and 2 doesn't need that). Without this part of the >>> host controller hardware doesn't get the clock I guess, or something >>> like that. You won't believe how much time we've wasted on this! >>> >> MUX_VAL(CP(ETK_CLK_ES2), (IEN | PTU | EN | M2)) /*MMC3_CLK*/\ >> >> Works Beautifully, Thank you so much. I have also burnt too much >> midnight oil on this problem. >> So looks like Overo MMC3 works like a champ! > > Might I suggest a kernel patch for this rather than fixing u-boot so that > all the midnight oil you've burnt does not have to be duplicated by others. Well I dont know how to answer that. Because the Mux architecture is slightly on the scary side. I personally have had success with it, but everytime you need to add a new pin functionality you have to update mux.h. I finally decided to just focus on having the MUX correct at boot up via u-boot.
I could just add the code to update the mux without using the mux architecture. I would appreciate some opinions on this. > > Thanks, > > Kevin > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
