From: Francisco Alecrim <francisco.alecrim@indt.org.br>
To: ext Paul Walmsley <paul@booyaka.com>
Cc: felipe.balbi@nokia.com, linux-omap@vger.kernel.org
Subject: Re: Missing mmc debounce clock (??)
Date: Fri, 18 Apr 2008 00:06:44 +0300 [thread overview]
Message-ID: <4807BBE4.8030100@indt.org.br> (raw)
In-Reply-To: <alpine.DEB.1.00.0804151013130.21271@utopia.booyaka.com>
ext Paul Walmsley wrote:
> On Tue, 15 Apr 2008, Francisco Alecrim wrote:
>
>
>> Hi Balbi,
>>
>> I was with the patch below in my queue when you told about your email at
>> linux-omap.
>>
>> I guess that is the correct solution.
>>
>> What do you think?
>>
>
> Eh, those clocks are identical to the existing MMC clocks.
>
> Seems better for the time being to modify omap_hsmmc.c:777 to test
> against !cpu_is_omap34xx() before emitting a warning?
>
You're right! Good catch!
>
> - Paul
>
>
--
Francisco Keppler Silva Alecrim - INdT
Phone: +55 92 2126-1017
prev parent reply other threads:[~2008-04-17 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 11:43 Missing mmc debounce clock (??) Felipe Balbi
2008-04-15 13:51 ` Francisco Alecrim
2008-04-15 13:57 ` Felipe Balbi
2008-04-15 16:17 ` Paul Walmsley
2008-04-17 21:06 ` Francisco Alecrim [this message]
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=4807BBE4.8030100@indt.org.br \
--to=francisco.alecrim@indt.org.br \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@booyaka.com \
/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