public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Ulf Hansson <ulf.hansson@stericsson.com>
Cc: linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH 0/4] mmc: core: Let the mmc_bus handle suspend|resume sequence
Date: Tue, 04 Jun 2013 18:53:45 +0900	[thread overview]
Message-ID: <51ADB929.9030705@samsung.com> (raw)
In-Reply-To: <1369918391-15277-1-git-send-email-ulf.hansson@stericsson.com>

Tested-by: Jaehoon Chung <jh80.chung@samsung.com>

Best Regards,
Jaehoon Chung

On 05/30/2013 09:53 PM, Ulf Hansson wrote:
> From: Ulf Hansson <ulf.hansson@linaro.org>
> 
> The MMC/SD/SDIO cards are registered on the mmc_bus and should from a power
> management perspective be controlled from there. As of today each and every
> host driver needs to issue mmc_suspend|resume_host from their respective
> .suspend|resume methods, which seems like an unnecessary requirement to
> put on them.
> 
> This patch set moves the responsiblity to suspend the cards into the mmc_bus.
> In this patch set, the mmc_suspend|resume_host functions are not removed, but
> will instead always return successful. As a separate patch build on top of
> this patch set, we shall remove the API:s together with updating each and
> every host driver.
> 
> Ulf Hansson (4):
>   mmc: core: Remove unnecessary check for the remove callback
>   mmc: core: Validate suspend prerequisites for SDIO at SUSPEND_PREPARE
>   mmc: core: Push common suspend|resume code into each bus_ops
>   mmc: core: Initiate suspend|resume from mmc bus instead of mmc host
> 
>  drivers/mmc/core/bus.c  |   28 ++++++++++++++-
>  drivers/mmc/core/core.c |   87 ++++++++---------------------------------------
>  drivers/mmc/core/core.h |    1 +
>  drivers/mmc/core/mmc.c  |    4 +++
>  drivers/mmc/core/sd.c   |    4 +++
>  drivers/mmc/core/sdio.c |   48 +++++++++++++++++++++++---
>  6 files changed, 94 insertions(+), 78 deletions(-)
> 


      parent reply	other threads:[~2013-06-04  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 12:53 [PATCH 0/4] mmc: core: Let the mmc_bus handle suspend|resume sequence Ulf Hansson
2013-05-30 12:53 ` [PATCH 1/4] mmc: core: Remove unnecessary check for the remove callback Ulf Hansson
2013-05-31  7:43   ` Jaehoon Chung
2013-05-31  8:11     ` Ulf Hansson
2013-05-31  8:22       ` Jaehoon Chung
2013-05-31  9:33         ` Ulf Hansson
2013-05-31 10:50           ` Jaehoon Chung
2013-05-31 15:05             ` Ulf Hansson
2013-05-30 12:53 ` [PATCH 2/4] mmc: core: Validate suspend prerequisites for SDIO at SUSPEND_PREPARE Ulf Hansson
2013-05-30 12:53 ` [PATCH 3/4] mmc: core: Push common suspend|resume code into each bus_ops Ulf Hansson
2013-05-30 12:53 ` [PATCH 4/4] mmc: core: Initiate suspend|resume from mmc bus instead of mmc host Ulf Hansson
2013-06-04  5:28   ` Jaehoon Chung
2013-06-04  8:34     ` Ulf Hansson
2013-06-04  8:47       ` Jaehoon Chung
2013-06-04  8:57         ` Ulf Hansson
2013-06-04  9:53 ` Jaehoon Chung [this message]

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=51ADB929.9030705@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=ulf.hansson@stericsson.com \
    /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