Skip to contentSkip to conversation

ARM: OMAP3: Add support for the IGEP v2 board (rev B)

PATCH Frédéric BEGOU 1 participant 1 message Nov 16, 2009 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 27 lines · Frédéric BEGOU

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 */
+};

Quoted 9 lines

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.

Hello,

OK I understand for your board.

I have my second MMC slot wired just like MMC1 : they are micro-SD slots wired with
- MMC2_CLK
- MMC2_CMD
- MMC2_DATA0
- MMC2_DATA1
- MMC2_DATA2
- MMC2_DATA3 , all 6 wired with a 4.7Kohm resistor to VMMC2 ;

VDD wired to VMMC2 and VSS to ground.
Add a capacitor between VMMC2 and the ground for the taste !

VMMC2 is 3.3V.

I've tested with a different combination of parameters in the twl4030_hsmmc_info structure in my board file, and now I'm stuck with the following :

static struct twl4030_hsmmc_info mmc[] = {
{
.mmc = 1,
.wires = 4,
.gpio_wp = -EINVAL,
},
{
.mmc = 2,
.wires = 4,
.transceiver = 0,
.ext_clock = 0,
.cover_only = 0,
.gpio_wp = -EINVAL,
.gpio_cd = -EINVAL,
},
{} /* Terminator */
};

MMC1 works well, but no success for MMC2.

Does someone please have pointers to documentation, apart from the twl4030_hsmmc_info structure header file ?

Thanks in advance.

--
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