On Fri, 2011-01-21 at 15:18 +0100, Koen Kooi wrote:
> Hi,
>
> I'm trying to bring up a wl1271 sdio expansion board on beagle with 2.6.37 and I'm running into a weird problem when enabling MMC_CAP_POWER_OFF_CARD.
>
> My patch basically does:
>
> --- a/arch/arm/mach-omap2/board-omap3beagle.c
> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
> @@ -270,7 +270,7 @@ static struct omap2_hsmmc_info mmc[] = {
> {
> .name = "wl1271",
> .mmc = 2,
> - .caps = MMC_CAP_4_BIT_DATA,
> + .caps = MMC_CAP_4_BIT_DATA | MMC_CAP_POWER_OFF_CARD,
>
> And does NOT touch mmc1. But after adding MMC_CAP_POWER_OFF_CARD I get tons of:
>
> [ 22.259490] mmcblk0: error -110 sending status comand
> [ 22.264617] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
> [ 22.273345] mmcblk0: error -110 transferring data, sector 2338228, nr 3, card status 0x0
> [ 22.281799] end_request: I/O error, dev mmcblk0, sector 2338228
> [ 22.288055] mmcblk0: error -110 sending status comand
> [ 22.293151] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
> [ 22.301879] mmcblk0: error -110 transferring data, sector 2338229, nr 2, card status 0x0
> [ 22.310363] end_request: I/O error, dev mmcblk0, sector 2338229
>
> When using mmcblk0p2 as rootfs. Attached is the complete patch. It looks a bit weird because it's using the expansionboard infrastucture I hacked together.
>
> I suspect that mmc2 is turning off the shared regulator, but I have various people claiming this code (minus the expansionboard detection) works with the same regulator setup, so I'm extremely puzzled.
>
> The CC: list was partially generated with the get_maintainer.pl script, apologies if I screwed it up.
I think Ohad is the right person to answer this question.
--
Cheers,
Luca.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
