[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGsJ_4zjRpEx_yLwXx74uipPN-Q2hun3AdLxKw2EYOy00cDm3Q@mail.gmail.com>
Date: Fri, 30 Sep 2011 07:16:57 +0800
From: Barry Song <21cnbao@...il.com>
To: Luca Tettamanti <kronos.it@...il.com>
Cc: Barry Song <Barry.Song@....com>, frank.hofmann@...tom.com,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
workgroup.linux@....com, rjw@...k.pl, pavel@....cz,
linux-pm@...ts.linux-foundation.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] PM: HIBERNATION: add resume_wait param to support
MMC-like devices as resume file
2011/9/29 Luca Tettamanti <kronos.it@...il.com>:
> On Thu, Sep 29, 2011 at 11:29 AM, Barry Song <Barry.Song@....com> wrote:
>> From: Barry Song <baohua.song@....com>
>>
>> Some devices like mmc are async detected very slow. For example,
>> drivers/mmc/host/sdhci.c launchs a 200ms delayed work to detect
>> mmc partitions then add disk.
>>
>> we do have wait_for_device_probe and scsi_complete_async_scans
>> before calling swsusp_check, but it is not enough to wait mmc.
>>
>> This patch adds resumewait kernel param just like rootwait so
>> that we have enough time to wait mmc ready. The differene is
>> here we wait for resume partition but rootwait waits for rootfs
>> partition.
>
> I assume that such a device would need "rootwait" to boot in the first
> place; why don't you "overload" the param to also enable waiting in
> the resume path?
not real. for an embedded product, the type of the rootfs, the place
of the rootfs and the way to mount rootfs are pretty flexible.
even though both rootfs and resume file use mmc, they will be in
different partitions at least. so i don't think rootwait can overload
resumewait.
>
> Luca
>
-barry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists