From: Luciano Coelho <coelho@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>, Ohad Ben-Cohen <ohad@wizery.com>
Cc: l-o List <linux-omap@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
"cjb@laptop.org" <cjb@laptop.org>
Subject: Re: Setting MMC_CAP_POWER_OFF_CARD on mmc2 leads to filesystem problems on mmc1
Date: Fri, 21 Jan 2011 16:49:02 +0200 [thread overview]
Message-ID: <1295621342.1925.139.camel@pimenta> (raw)
In-Reply-To: <E6C3A477-63F7-4BA0-8E6B-A35A53B3AEA1@dominion.thruhere.net>
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.
next prev parent reply other threads:[~2011-01-21 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 14:18 Setting MMC_CAP_POWER_OFF_CARD on mmc2 leads to filesystem problems on mmc1 Koen Kooi
2011-01-21 14:49 ` Luciano Coelho [this message]
2011-01-22 10:36 ` Ohad Ben-Cohen
2011-01-22 15:30 ` Koen Kooi
2011-01-22 15:47 ` Ohad Ben-Cohen
2011-02-02 0:11 ` Tony Lindgren
2011-02-02 8:01 ` Ohad Ben-Cohen
2011-02-03 1:08 ` Tony Lindgren
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=1295621342.1925.139.camel@pimenta \
--to=coelho@ti.com \
--cc=cjb@laptop.org \
--cc=koen@dominion.thruhere.net \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=ohad@wizery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox