public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Balaji T K <balajitk@ti.com>
Cc: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org,
	cjb@laptop.org, tony@atomide.com, madhu.cr@ti.com,
	b-cousson@ti.com
Subject: Re: [PATCH 1/3] MMC: OMAP: HSMMC: Remove lazy_disable
Date: Wed, 22 Jun 2011 11:26:41 -0700	[thread overview]
Message-ID: <87k4cdrace.fsf@ti.com> (raw)
In-Reply-To: <1308752314-32079-2-git-send-email-balajitk@ti.com> (Balaji T. K.'s message of "Wed, 22 Jun 2011 19:48:32 +0530")

Balaji T K <balajitk@ti.com> writes:

> lazy_disable framework in OMAP HSMMC manages multiple low power states
> and Card is powered off after inactivity time of 8 seconds.
> Based on previous discussion on the list Card power(regulator)

needs some punctuation for readability.

> handling (when to power OFF/ON) should ideally be handled by core layer.

So are you working on the core layer replacement for this?  If not, is
there a plan or owner for this?

> Remove usage of lazy disable to allow core layer _only_ to handle card power.
> With the removal of lazy disable framework, MMC regulators
> are left ON until MMC_POWER_OFF via set_ios.
>
> Signed-off-by: Balaji T K <balajitk@ti.com>

[...]

> @@ -2080,10 +1848,7 @@ static int __init omap_hsmmc_probe(struct platform_device *pdev)
>  	platform_set_drvdata(pdev, host);
>  	INIT_WORK(&host->mmc_carddetect_work, omap_hsmmc_detect);
>  
> -	if (mmc_slot(host).power_saving)
> -		mmc->ops	= &omap_hsmmc_ps_ops;
> -	else
> -		mmc->ops	= &omap_hsmmc_ops;
> +	mmc->ops	= &omap_hsmmc_ops;

I guess the _ps_ops struct is now completely unused so should probably
be removed in this patch also.

Kevin


  reply	other threads:[~2011-06-22 18:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 14:18 [PATCH 0/3] OMAP: HSMMC: cleanup and runtime pm Balaji T K
2011-06-22 14:18 ` [PATCH 1/3] MMC: OMAP: HSMMC: Remove lazy_disable Balaji T K
2011-06-22 18:26   ` Kevin Hilman [this message]
2011-06-23 12:31     ` T Krishnamoorthy, Balaji
2011-06-22 14:18 ` [PATCH 2/3] MMC: OMAP: HSMMC: add runtime pm support Balaji T K
2011-06-22 18:38   ` Kevin Hilman
2011-06-23 12:31     ` T Krishnamoorthy, Balaji
2011-06-23 14:50       ` Kevin Hilman
2011-06-28 17:22   ` Paul Walmsley
2011-06-28 17:48     ` T Krishnamoorthy, Balaji
2011-06-28 18:41       ` Paul Walmsley
2011-06-29 14:17         ` T Krishnamoorthy, Balaji
2011-06-29 14:42           ` Paul Walmsley
2011-06-29 16:14             ` T Krishnamoorthy, Balaji
2011-06-29 19:04               ` Paul Walmsley
2011-06-29 15:38           ` Paul Walmsley
2011-06-29 16:34             ` S, Venkatraman
2011-06-29 20:07               ` Paul Walmsley
2011-06-30  5:20                 ` S, Venkatraman
2011-06-28 20:30       ` Kevin Hilman
2011-06-29 14:33         ` T Krishnamoorthy, Balaji
2011-06-29 17:39           ` Kevin Hilman
2011-06-30  0:40           ` Paul Walmsley
2011-06-30  5:26             ` S, Venkatraman
2011-06-22 14:18 ` [PATCH 3/3] MMC: OMAP: HSMMC: Remove unused iclk Balaji T K
2011-06-22 16:27   ` Cousson, Benoit
2011-06-27 14:41     ` T Krishnamoorthy, Balaji
2011-06-22 16:05 ` [PATCH 0/3] OMAP: HSMMC: cleanup and runtime pm Cousson, Benoit

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=87k4cdrace.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balajitk@ti.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=tony@atomide.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