From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: linux-kernel@vger.kernel.org, beagleboard@googlegroups.com,
openembedded-devel@openembedded.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] drivers/mmc/core/core.c: extend limit
Date: Sun, 5 Apr 2009 20:57:27 +0200 [thread overview]
Message-ID: <20090405205727.7a86d61b@mjolnir.ossman.eu> (raw)
In-Reply-To: <alpine.LNX.2.00.0903252248430.32070@linux-suse.site>
On Wed, 25 Mar 2009 23:03:28 +0100 (CET)
Frans Meulenbroeks <fransmeulenbroeks@gmail.com> wrote:
>
> This did not help me as the limit was already at 300000. However, I
> decided to raise the limit to 500000. Still no go so I also doubled the
> read limit from 100000 to 200000. After that the cards work without
> problem. Changing the write timing back to 300000 brought the problem back
> so apparently both timings need to be extended. Attached is the patch I
> used for this. As it is a timeout limit value, it should not harm anyone,
> and a longer timeout at least allows more cards to be used.
>
Unfortunately some controllers cannot cope with huge timeouts and will
complain. And such a huge timeout shouldn't be needed (and they weren't
any larger in .27).
>
> What somewhat troubles me is that this worked in .27, so it might be this
> patch does not address the root cause. Then again this is the best I can
> do. If someone has a better solution, I am more than happy to test it.
>
Indeed. Have you enabled MMC_DEBUG and checked that the controller
actually follows the configured timeouts?
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
prev parent reply other threads:[~2009-04-05 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 22:03 Frans Meulenbroeks
2009-04-05 18:57 ` Pierre Ossman [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=20090405205727.7a86d61b@mjolnir.ossman.eu \
--to=drzeus-mmc@drzeus.cx \
--cc=beagleboard@googlegroups.com \
--cc=fransmeulenbroeks@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=openembedded-devel@openembedded.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
all inboxes | Powered by JetHome®