[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAME+o4=WrfpvJo=jN1KZ_JHnYq9Frfk3EPcwtG10=aCwrbY+Rw@mail.gmail.com>
Date: Mon, 24 Jun 2013 12:58:39 -0700
From: Zoran Markovic <zoran.markovic@...aro.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Colin Cross <ccross@...roid.com>,
lkml <linux-kernel@...r.kernel.org>, linux-mmc@...r.kernel.org,
San Mehat <san@...gle.com>,
John Stultz <john.stultz@...aro.org>,
Chris Ball <cjb@...top.org>,
Johan Rudholm <johan.rudholm@...ricsson.com>,
Jaehoon Chung <jh80.chung@...sung.com>,
Konstantin Dorfman <kdorfman@...eaurora.org>,
Guennadi Liakhovetski <g.liakhovetski@....de>,
Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC PATCH] mmc: Enable wakeup_sources for mmc core
>> This patch is ported from the Android common tree, so you've probably
>> been using it.
>
> We removed more or less all Android code in the mmc subsystem, since
> it just didn't work. :-)
>
> The "deferred resume" was very useful though, so after some rework we
> kept it and could then improve the system resume time significantly.
For what it's worth, I fixed one bug I noticed in the Android kernel:
if a system has a non-removable MMC device, a suspend/resume cycle on
this device would hold a wake lock forever. This was a visible issue
on the panda board I am using.
If there are doubts on whether or not the system should stay awake
during a MMC mount, we have the option to make the calls to
wakeup_source_register/unregister configurable. Skipping these calls
would leave the .ws field NULL, in which case
__pm_stay_awake/__pm_relax/__pm_wakeup_event would do nothing.
Thoughts?
- Zoran
--
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