From: Francisco Alecrim <francisco.alecrim@indt.org.br>
To: Madhusudhan Chikkature Rajashekar <madhu.cr@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [RFC/PATH] OMAP: HSMMC: Fixes for 1.8V MMC2 interface
Date: Wed, 02 Apr 2008 03:46:44 +0300 [thread overview]
Message-ID: <47F2D774.2060308@indt.org.br> (raw)
In-Reply-To: <20080401161617.GA28624@ubuntu-workstation>
ext Seth Forshee wrote:
> On Tue, Apr 01, 2008 at 08:44:47PM +0530, Madhusudhan Chikkature Rajashekar wrote:
>
>> Hi,
>>
>> I did not see any board level code to power up the second slot along with this patch.
>> Where is the code that enables 1.8V to the second slot?
>>
>
> I am working with a custom board that isn't supported in the git repo, and I
> don't have access to any other board that I could test such changes with.
> These are just the chages I found were necessary to support the 1.8V-only
> host, regardless of whatever board support is needed.
That's the same problem here!! I have a custom board too!! However,
pushing patches [1] and [2] we will be able to enable the second
controller with some modifications in board-sdp-mmc.c.
[1] - OMAP: HSMMC: Fixes for 1.8V MMC2 interface
[2] - [PATCH 1/1] PLAT: OMAP: Add device configuration to support second
HSMMC slot on OMAP 2430 and 3430 boards.
--
Francisco Keppler Silva Alecrim - INdT
Phone: +55 92 2126-1017
Mobile: +55 92 9152-7000
next prev parent reply other threads:[~2008-04-02 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 2:31 [RFC/PATH] OMAP: HSMMC: Fixes for 1.8V MMC2 interface Seth Forshee
2008-03-31 20:45 ` Francisco Alecrim
2008-04-01 0:51 ` Seth Forshee
2008-04-01 15:14 ` Madhusudhan Chikkature Rajashekar
2008-04-01 16:16 ` Seth Forshee
2008-04-02 0:46 ` Francisco Alecrim [this message]
2008-04-02 4:17 ` Madhusudhan Chikkature Rajashekar
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=47F2D774.2060308@indt.org.br \
--to=francisco.alecrim@indt.org.br \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.