[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDyKFoX-ioDVVkfQ21epJyTqQD98xvsqBR1FXzgP9bN6_Zxjg@mail.gmail.com>
Date: Sun, 23 Jun 2013 11:28:01 +0200
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Colin Cross <ccross@...roid.com>
Cc: Zoran Markovic <zoran.markovic@...aro.org>,
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
On 19 June 2013 19:29, Colin Cross <ccross@...roid.com> wrote:
> On Wed, Jun 19, 2013 at 7:21 AM, Ulf Hansson <ulf.hansson@...aro.org> wrote:
>> It seems like a bad idea that an insertion of an SD card should
>> trigger the display to be light up. That is indirectly in principle
>> what you suggest should happen from user space once a new SD card is
>> found. Right?
>
> Most likely what will happen is the system will mount the sdcard, and
> if necessary start the media scanner so that the user can see their
> media on the sd card when they turn the screen on. But that is mostly
> irrelevant, the point is that the event needs to be passed to
> userspace to allow it to make the decision in a timely fashion.
>
>> I have been working with Android for several years, we never used this
>> kind of setup. Instead we wait for the user to press the "display on"
>> button. At that time the confirmation will be received. Not saying
>> that this is the only way of doing it, but it seems to be an accepted
>> solution for all our customers.
>
> 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.
>
>> I agree to that this patch should have negligible impact though - if
>> we get things right. I will try to review the code in more detail
>> soon.
>>
>> Kind regards
>> Ulf Hansson
>>
--
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