public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: John Sarman <johnsarman@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Fwd: MMC3 Overo
Date: Wed, 05 Aug 2009 09:25:39 -0700	[thread overview]
Message-ID: <873a866xdo.fsf@deeprootsystems.com> (raw)
In-Reply-To: <bb2708720908050902o39c67430pbdcd12e9b835ab70@mail.gmail.com> (John Sarman's message of "Wed\, 5 Aug 2009 12\:02\:01 -0400")

John Sarman <johnsarman@gmail.com> writes:

> ---------- Forwarded message ----------
> From: John Sarman <johnsarman@gmail.com>
> Date: Wed, Aug 5, 2009 at 12:01 PM
> Subject: Re: MMC3 Overo
> To: Grazvydas Ignotas <notasas@gmail.com>
>
>
> On Wed, Aug 5, 2009 at 4:32 AM, Grazvydas Ignotas<notasas@gmail.com> 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.

Thanks,

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-08-05 16:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 15:49 MMC3 Overo John Sarman
2009-07-30 19:23 ` John Sarman
2009-08-03  1:20   ` Paul Walmsley
2009-08-03 10:33     ` John Sarman
     [not found]       ` <52AC0DF6-BA95-421B-8C56-5F3DC62279DF@mac.com>
     [not found]         ` <bb2708720908030356p6d7b1cdegf0bd8c39a5c4ecd9@mail.gmail.com>
2009-08-03 10:57           ` Fwd: " John Sarman
2009-08-03 11:11       ` Paul Walmsley
2009-08-04 12:21     ` John Sarman
2009-08-05  8:32 ` Grazvydas Ignotas
     [not found]   ` <bb2708720908050901lbc67b1cx5a75a7667fa36fd1@mail.gmail.com>
2009-08-05 16:02     ` Fwd: " John Sarman
2009-08-05 16:25       ` Kevin Hilman [this message]
2009-08-05 16:35         ` John Sarman
2009-08-05 17:51           ` Steve Sakoman
2009-08-05 17:56             ` Gadiyar, Anand
2009-08-05 17:58             ` Kevin Hilman
2009-08-05 18:21               ` Steve Sakoman
2009-08-05 18:35                 ` Kevin Hilman
2009-08-05 18:55                   ` Philip Balister
2009-08-06  2:13                     ` Hunyue Yau
     [not found]                   ` <bb2708720908051229x49f10094w9b19b468d4bfaec8@mail.gmail.com>
2009-08-06  2:02                     ` John Sarman
2009-08-06  6:44                       ` Tony Lindgren
2009-08-06 14:30                       ` Kevin Hilman
2009-08-06 14:44                         ` Vladimir Pantelic
2009-08-06 15:16                           ` Kevin Hilman
2009-08-06 15:35                             ` Steve Sakoman
2009-08-06 15:09                         ` Philip Balister
2009-08-06 16:09                           ` Peter Barada
2009-08-07  8:21                             ` Tony Lindgren
2009-08-07  9:24                               ` Vladimir Pantelic
2009-08-07  9:55                                 ` Tony Lindgren
2009-08-07 13:24                                   ` Steve Sakoman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873a866xdo.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=johnsarman@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox