From: Daniel Toussaint <daniel@dmhome.net>
To: "Frédéric BEGOU" <fbegou@sios.fr>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2 (for-next)] ARM: OMAP3: Add support for the IGEP v2 board (rev B)
Date: Sun, 15 Nov 2009 01:13:22 +0800 [thread overview]
Message-ID: <4AFEE532.2060407@dmhome.net> (raw)
In-Reply-To: <4AFD8DBA.6040906@sios.fr>
Frédéric BEGOU wrote:
> Hello,
>
> For what I've seen on the Internet concerning your card, there is only
> one MMC card reader.
> Besides, there is the following piece of code :
>
>> +static struct twl4030_hsmmc_info mmc[] = {
>> + {
>> + .mmc = 1,
>> + .wires = 4,
>> + .gpio_cd = -EINVAL,
>> + .gpio_wp = -EINVAL,
>> + },
>> + {
>> + .mmc = 2,
>> + .wires = 4,
>> + .gpio_cd = -EINVAL,
>> + .gpio_wp = -EINVAL,
>> + },
>> + {} /* Terminator */
>> +};
>
> Maybe I am mistaken, but doesn't that mean there are two MMC cards ?
>
> I am interested in the subject, as I am trying to write my own board
> file for our custom, beagleboard-based card, with no success so far
> concerning the second MMC reader...
Well, it seems that the board is question has a WIFI module connected to
the second mmc. What is your problem right now ? Remember that all three
MMC slots are different in what kind of voltage they can drive.
--
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
next prev parent reply other threads:[~2009-11-14 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 16:47 [PATCH 1/2 (for-next)] ARM: OMAP3: Add support for the IGEP v2 board (rev B) Frédéric BEGOU
2009-11-14 17:13 ` Daniel Toussaint [this message]
[not found] <4B015F12.7080709@sios.fr>
2009-11-16 14:31 ` Frédéric BEGOU
-- strict thread matches above, loose matches on Subject: below --
2009-11-13 12:29 Enric Balletbo i Serra
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=4AFEE532.2060407@dmhome.net \
--to=daniel@dmhome.net \
--cc=fbegou@sios.fr \
--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