linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zoran Markovic <zoran.markovic@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Colin Cross <ccross@android.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mmc@vger.kernel.org, San Mehat <san@google.com>,
	John Stultz <john.stultz@linaro.org>, Chris Ball <cjb@laptop.org>,
	Johan Rudholm <johan.rudholm@stericsson.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Konstantin Dorfman <kdorfman@codeaurora.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] mmc: Enable wakeup_sources for mmc core
Date: Thu, 1 Aug 2013 00:42:28 -0700	[thread overview]
Message-ID: <CAME+o4kpsPkoTpS7_0STDpMQpZr0KyfD1prbYYJs147-5DiMkg@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFpKYeqoFn=S6P2tu1s2C28daCh4vcHTUCCRUOx2_MHShg@mail.gmail.com>

Ulf,
I got confirmation from Broadcom that all cell phone reference designs
have card insert/removal configured as a wakeup IRQ. Unless our
customers change that - which I doubt - this results in a considerable
number of products implementing this feature.

Please let me know how you wish to proceed.

Cheers,
Zoran

On 26 June 2013 13:57, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> On 24 June 2013 21:58, Zoran Markovic <zoran.markovic@linaro.org> 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

  reply	other threads:[~2013-08-01  7:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 17:56 [RFC PATCH] mmc: Enable wakeup_sources for mmc core Zoran Markovic
2013-06-14 12:11 ` Ulf Hansson
2013-06-14 18:42   ` Zoran Markovic
2013-06-14 20:52     ` Colin Cross
2013-06-17 14:22       ` Ulf Hansson
2013-06-17 18:33         ` Colin Cross
2013-06-18 13:17           ` Ulf Hansson
2013-06-18 17:15             ` Colin Cross
2013-06-19 14:21               ` Ulf Hansson
2013-06-19 17:29                 ` Colin Cross
2013-06-23  9:28                   ` Ulf Hansson
2013-06-24 19:58                     ` Zoran Markovic
2013-06-26 20:57                       ` Ulf Hansson
2013-08-01  7:42                         ` Zoran Markovic [this message]
2013-08-22 17:08                           ` Zoran Markovic
2013-08-23  7:15                             ` Ulf Hansson
2013-08-23  8:12 ` Ulf Hansson
2013-09-05 21:54   ` Zoran Markovic

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=CAME+o4kpsPkoTpS7_0STDpMQpZr0KyfD1prbYYJs147-5DiMkg@mail.gmail.com \
    --to=zoran.markovic@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=ccross@android.com \
    --cc=cjb@laptop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=jh80.chung@samsung.com \
    --cc=johan.rudholm@stericsson.com \
    --cc=john.stultz@linaro.org \
    --cc=kdorfman@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=san@google.com \
    --cc=tj@kernel.org \
    --cc=ulf.hansson@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;
as well as URLs for NNTP newsgroup(s).