From: Pierre Ossman <pierre@ossman.eu>
To: dsaxena@plexity.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MMC: Add 400ms to CAFE SD controller resume path
Date: Fri, 22 May 2009 13:51:50 +0200 [thread overview]
Message-ID: <20090522135150.7e0716d6@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090513200556.GA7882@plexity.net>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Wed, 13 May 2009 20:05:56 +0000
Deepak Saxena <dsaxena@plexity.net> wrote:
>
> The CAFE SD controller takes a long time to completely resume
> and w/o this patch, we do not redetect an existing card but
> instead detect it as a new one. Even with MMC_UNSAFE_RESUME
> enabled, this leads to the partition table on the device being
> wiped out.
>
> See http://dev.laptop.org/ticket/6532 for gory details.
>
> Signed-off-by: Deepak Saxena <dsaxena@laptop.org>
>
Reading through that report, I don't believe you properly worked around
the bug. You only avoid bug 1339, but that's only mildly related.
What this workaround does is to make sure that MMC_UNSAFE_RESUME
actually works. But if you change cards during suspend, the VFS bug
should reappear and you'll corrupt the partition table.
And as for 1339, has there been any more work done on why this problem
doesn't appear in OFW? I'd be a lot happier if we could make things
work without artificial delays.
RGds
--
-- Pierre Ossman
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-05-22 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 20:05 Deepak Saxena
2009-05-22 11:51 ` Pierre Ossman [this message]
2009-05-28 8:36 ` Andrew Morton
2009-05-28 8:48 ` Pierre Ossman
2009-06-04 23:33 ` Deepak Saxena
2009-06-13 10:34 ` Pierre Ossman
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=20090522135150.7e0716d6@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.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®