From: lauri.hintsala@bluegiga.com (Lauri Hintsala)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: mxs-mmc: implement broken-cd
Date: Mon, 17 Sep 2012 17:40:51 +0300 [thread overview]
Message-ID: <50573673.6050506@bluegiga.com> (raw)
In-Reply-To: <m3boh4n3z7.fsf@pullcord.laptop.org>
Hi,
On 09/17/2012 05:01 PM, Chris Ball wrote:
> Hi,
>
> On Mon, Sep 17 2012, Lauri Hintsala wrote:
>> Is it OK to use broken-cd? broken-cd feature is documented as "There
>> is no card detection available; polling must be used". In this case
>> the card detect is not broken but it is unrouted so it is unavailable.
>>
>> Documentation about broken-cd has been added by commit:
>> https://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commitdiff;h=abe1e05da365350ac282ba5f6831aae13d97074e
>
> I'm having trouble following the problem; it sounds like perhaps all you
> need is:
>
> if (of_find_property(np, "non-removable", NULL))
> mmc->caps |= MMC_CAP_NONREMOVABLE;
>
> Have you tried that?
Yes I have and it does not work. Current mxs-mmc driver uses polling
method and it reads the CARD_DETECT bit of STATUS register. In our case
card detect is signal is unrouted so SDIO device is never detect.
Another problem with NONREMOVABLE feature is in case where power cycle
or reset is done for SDIO device. A device drive doesn't detect HW
reset. After reset the device driver is still in running state and it
does not reinitialize the device. So after reset device stops to work.
Lauri
prev parent reply other threads:[~2012-09-17 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 11:45 [PATCH] mmc: mxs-mmc: implement broken-cd Lauri Hintsala
2012-09-10 6:08 ` Shawn Guo
2012-09-10 10:04 ` Lauri Hintsala
2012-09-10 13:50 ` Shawn Guo
2012-09-20 4:45 ` Lauri Hintsala
2012-09-10 14:58 ` Matt Sealey
2012-09-12 14:06 ` Lauri Hintsala
2012-09-17 13:43 ` Lauri Hintsala
2012-09-17 14:01 ` Chris Ball
2012-09-17 14:40 ` Lauri Hintsala [this message]
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=50573673.6050506@bluegiga.com \
--to=lauri.hintsala@bluegiga.com \
--cc=linux-arm-kernel@lists.infradead.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