public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Tushar Behera <tushar.behera@linaro.org>
To: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-s3c: Remove old and misprototyped suspend operations
Date: Mon, 19 Dec 2011 10:15:27 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111219T110819-762@post.gmane.org> (raw)
In-Reply-To: 87zkfckvve.fsf@laptop.org

Hi,

Chris Ball <cjb <at> laptop.org> writes:

> 
> Hi,
> 
> On Tue, Nov 29 2011, Jaehoon Chung wrote:
> > Acked-by: Jaehoon Chung <jh80.chung <at> samsung.com>
> >
> > On 11/22/2011 03:00 AM, Mark Brown wrote:
> >
> >> Now that the driver is using dev_pm_ops the suspend operations in the
> >> platform_driver structure won't get called so don't need to be there,
> >> and certainly shouldn't be the same function as dev_pm_ops since the
> >> signatures are different.
> >> 
> >> Signed-off-by: Mark Brown <broonie <at> opensource.wolfsonmicro.com>

On Origen board (based on EXYNOS4210), the primary filesystem is on a
SD/MMC card. When tested with v3.2-rc6 kernel, the system doesn't resume
properly.

After resume, it keeps printing following message and the filesystem never
comes up.

mmc0: Timeout waiting for hardware interrupt.

If this patch is reverted, the system is able to mount the filesystem 
successfully.    

Am I missing something?





  reply	other threads:[~2011-12-19 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 18:00 [PATCH] mmc: sdhci-s3c: Remove old and misprototyped suspend operations Mark Brown
2011-11-29 15:05 ` Jaehoon Chung
2011-12-01 18:08   ` Chris Ball
2011-12-19 10:15     ` Tushar Behera [this message]
2011-12-25  2:29       ` Chris Ball
2011-12-26  1:54         ` Jaehoon Chung
2011-12-26  5:05           ` Tushar Behera
2011-12-26  5:23             ` Jaehoon Chung
2011-12-26  6:00               ` Tushar Behera

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=loom.20111219T110819-762@post.gmane.org \
    --to=tushar.behera@linaro.org \
    --cc=linux-mmc@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