All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: print debug messages for runtime PM actions
Date: Mon, 18 Jul 2011 22:31:43 -0400	[thread overview]
Message-ID: <m2pql79f1s.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110717153841.D4BF29D401C@zog.reactivated.net> (Daniel Drake's message of "Sun, 17 Jul 2011 16:38:41 +0100 (BST)")

Hi Dan,

On Sun, Jul 17 2011, Daniel Drake wrote:
> At
> http://www.mail-archive.com/linux-mmc@vger.kernel.org/msg08371.html
> we found and fixed a bug where mmc's runtime power management functions
> were not being called. We have now also made improvements to the SDIO
> powerup routine which could possibly mask this kind of issue in future.
>
> Add debug messages to the runtime PM hooks so that it is easy to verify
> if and when runtime PM is happening.
>
> Signed-off-by: Daniel Drake <dsd@laptop.org>
> ---
>  drivers/mmc/core/core.c |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
>
> For linux-3.1.
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 0a04886..ad0c55a 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -1664,6 +1664,10 @@ int mmc_power_save_host(struct mmc_host *host)
>  {
>  	int ret = 0;
>  
> +#ifdef CONFIG_MMC_DEBUG
> +	pr_info("%s: %s: powering down\n", mmc_hostname(host), __func__);
> +#endif
> +

Did you consider just:

	pr_debug("%s: %s: powering down\n", mmc_hostname(host), __func__);

which gets you the same CONFIG_MMC_DEBUG semantics?  (The messages will
be at the debug loglevel rather than info, but that sounds right to me.)

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-07-19  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 15:38 [PATCH] mmc: print debug messages for runtime PM actions Daniel Drake
2011-07-19  2:31 ` Chris Ball [this message]
2011-07-20 16:36   ` Daniel Drake
2011-07-20 16:44     ` Chris Ball

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=m2pql79f1s.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=dsd@laptop.org \
    --cc=linux-mmc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.