Our team found out there is a hardware problem in our design that prevents the WF111 chip to be properly powered up.
Regardless, there is another thing that concerns me.
When I connect an oscilloscope to the clock line I never see a signal when the driver is loaded. Seems to me that even if the chip were on I still wouldn't be able to communicate with it...
Since I already showed the pinmux structure, here is the rest of the MMC configuration I use:
static struct omap2_hsmmc_info am335x_mmc[] __initdata = { { .mmc = 1, .caps = MMC_CAP_4_BIT_DATA, .gpio_cd = GPIO_TO_PIN(2, 26), /* GPIO2.26 */ .ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34, /* 3V3 */ }, { .mmc = 3, .name = "unifi", .caps = MMC_CAP_4_BIT_DATA | MMC_CAP_POWER_OFF_CARD, .nonremovable = true, .gpio_cd = -EINVAL, .gpio_wp = -EINVAL, .ocr_mask = MMC_VDD_165_195, /* 1V8 */ }, {} /* Terminator */ };In my desing, MMC0 is connected to a SD card slot, MMC1 communicates with the NAND chip and the MMC2 is the WiFi SDIO bus.
unifi is the driver's name and the remaining was again based on the configuration the EVM uses in it's board configuration file.
Would the pinmux (as shown in the post above) and this structure be enough to configure the bus? What am I missing that would prevent a clock signal from being sent?
DAVI