mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: John Stultz <john.stultz@linaro.org>
Cc: Ruchi Kandoi <kandoiruchi@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	ghackmann@google.com, toddpoynor@google.com,
	Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH v4] power: add an API to log wakeup reasons
Date: Mon, 07 Jul 2014 22:09:28 +0200	[thread overview]
Message-ID: <1513900.gylJAouuZq@vostro.rjw.lan> (raw)
In-Reply-To: <CANcMJZAm+TfX5W_AMSECBTb8tAzts9_YtOjCXGhmy4SgPAjYqg@mail.gmail.com>

On Monday, July 07, 2014 03:02:18 PM John Stultz wrote:
> On Thu, Mar 13, 2014 at 6:05 PM, Ruchi Kandoi <kandoiruchi@google.com> wrote:
> > For power management diagnostic purposes, it is often useful to know
> > what interrupts are frequently waking the system from low power
> > suspend mode, especially on battery-powered consumer electronics
> > devices that are expected to spend much of their time in low-power
> > suspend while not in active use.  For example, reduced battery life on
> > a mobile phone may be caused in part by frequent wakeups by broadcast
> > traffic on a busy wireless LAN even while the screen is off and the
> > phone not in active use.
> >
> > Add API log_wakeup_reason() exposes it to userspace via the sysfs path
> > /sys/kernel/wakeup_reasons/last_resume_reason. This API would be called
> > from the paltform specific, or from the driver for the interrupt controller,
> > when the system resumes because of an IRQ. It logs the reasons which caused
> > the system to wakeup from the low-power mode.
> >
> > This information can be collected by userspace as part of the accounting
> > kept on power consumption.
> 
> Rafael,
>    I realize its been awhile here, but seeing as discussion on this
> petered out somewhat ambiguously, I was curious if your thoughts on
> using wakeup_sources for this was considered a prereq for further
> discussion or if it was a softer thought experiment?

It really was softer at that time, but today that we have the "freeze"
sleep state where wakeup sources really are used for wakeup it would make
more sense to used them here too.

Rafael


      reply	other threads:[~2014-07-07 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 17:05 Ruchi Kandoi
2014-07-07 13:02 ` John Stultz
2014-07-07 20:09   ` Rafael J. Wysocki [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=1513900.gylJAouuZq@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=amit.kucheria@linaro.org \
    --cc=ghackmann@google.com \
    --cc=john.stultz@linaro.org \
    --cc=kandoiruchi@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=toddpoynor@google.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

all inboxes | Powered by JetHome®