Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752873Ab3FZU5Q (ORCPT ); Wed, 26 Jun 2013 16:57:16 -0400 Received: from mail-vc0-f178.google.com ([209.85.220.178]:60257 "EHLO mail-vc0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751557Ab3FZU5O (ORCPT ); Wed, 26 Jun 2013 16:57:14 -0400 MIME-Version: 1.0 In-Reply-To: References: <1371146190-16786-1-git-send-email-zoran.markovic@linaro.org> Date: Wed, 26 Jun 2013 22:57:13 +0200 Message-ID: Subject: Re: [RFC PATCH] mmc: Enable wakeup_sources for mmc core From: Ulf Hansson To: Zoran Markovic Cc: Colin Cross , lkml , linux-mmc@vger.kernel.org, San Mehat , John Stultz , Chris Ball , Johan Rudholm , Jaehoon Chung , Konstantin Dorfman , Guennadi Liakhovetski , Tejun Heo , Andrew Morton Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1650 Lines: 42 On 24 June 2013 21:58, Zoran Markovic wrote: >>> 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. Even if we make this feature configurable, I can't see any host driver that would benefit from it as of today. The reason is simply that host drivers do not configure it's card detect irq as a wakeup irq. Myself is also having quite hard to see the benefit of doing that, but I don't know all the use cases. Let's see if we can get someone else to provide input... > > Thoughts? > > - Zoran Kind regards Ulf Hansson -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/