From: Jaehoon Chung <jh80.chung@samsung.com>
To: Chris Ball <cjb@laptop.org>
Cc: Tushar Behera <tushar.behera@linaro.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-s3c: Remove old and misprototyped suspend operations
Date: Mon, 26 Dec 2011 10:54:38 +0900 [thread overview]
Message-ID: <4EF7D3DE.5060907@samsung.com> (raw)
In-Reply-To: <m239c9z8mk.fsf@bob.laptop.org>
Hi Tushar.
I also tested this patch with Samsung-SoC.
But i didn't find the below message
"mmc0: Timeout waiting for hardware interrupt."
I didn't understand what is that differ with previously code?
(just using dev_pm_ops..)
Thanks,
Jaehoon Chung
On 12/25/2011 11:29 AM, Chris Ball wrote:
> Hi,
>
> On Mon, Dec 19 2011, Tushar Behera 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?
>
> Mark/Jaehoon? This looks very bad.
>
> - Chris.
next prev parent reply other threads:[~2011-12-26 1:54 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
2011-12-25 2:29 ` Chris Ball
2011-12-26 1:54 ` Jaehoon Chung [this message]
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=4EF7D3DE.5060907@samsung.com \
--to=jh80.chung@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=kgene.kim@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tushar.behera@linaro.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