All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] debugfs entries for PM counters
Date: Wed, 29 Oct 2008 11:22:52 -0700	[thread overview]
Message-ID: <4908A9FC.4090001@deeprootsystems.com> (raw)
In-Reply-To: <1223995198-19985-1-git-send-email-peter.de-schrijver@nokia.com>

Peter 'p2' De Schrijver wrote:
> This patchset adds 2 debugfs entries for power management counters.
> pm_debug/count indicates how many times each powerdomain entered each state
> (On, Inactive, Retention, Off).
> pm_debug/time indicates how much time each powerdomain spent per state.
> 
> Peter 'p2' De Schrijver (3):
>   Add closures to clkdm_for_each.
>   Add pm-debug counters
>   Hook into powerdomain code
> 

Thanks, pulling this series into next PM branch.

Kevin

  parent reply	other threads:[~2008-10-29 18:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 14:39 [PATCH 0/3] debugfs entries for PM counters Peter 'p2' De Schrijver
2008-10-14 14:39 ` [PATCH 1/3] Add closures to clkdm_for_each and pwrdm_for_each Peter 'p2' De Schrijver
2008-10-14 14:39   ` [PATCH 2/3] Add pm-debug counters Peter 'p2' De Schrijver
2008-10-14 14:39     ` [PATCH 3/3] Hook into powerdomain code Peter 'p2' De Schrijver
2008-10-14 19:55       ` Paul Walmsley
2008-10-15 14:32         ` Peter 'p2' De Schrijver
2008-10-14 19:47     ` [PATCH 2/3] Add pm-debug counters Paul Walmsley
2008-10-15  6:12     ` Högander Jouni
2008-10-15  9:54       ` Tero.Kristo
2008-10-14 19:50   ` [PATCH 1/3] Add closures to clkdm_for_each and pwrdm_for_each Paul Walmsley
2008-10-29 18:22 ` Kevin Hilman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-15 15:13 [PATCH 0/3] debugfs entries for PM counters Peter 'p2' De Schrijver

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=4908A9FC.4090001@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.de-schrijver@nokia.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 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.