From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Ruchi Kandoi <kandoiruchi@google.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
ghackmann@google.com, john.stultz@linaro.org,
toddpoynor@google.com
Subject: Re: [PATCH v3] power: add an API to log wakeup reasons
Date: Thu, 13 Mar 2014 23:18:14 +0100 [thread overview]
Message-ID: <1559784.2mnpODc5zV@vostro.rjw.lan> (raw)
In-Reply-To: <1394653598-17143-1-git-send-email-kandoiruchi@google.com>
Hi,
I saw the v4, but I don't have it handy, so replying here.
On Wednesday, March 12, 2014 12:46:38 PM Ruchi Kandoi 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.
So what exactly is wrong with using wakeup sources for this purpose?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-03-13 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 19:46 Ruchi Kandoi
2014-03-12 19:50 ` Joe Perches
2014-03-13 22:18 ` Rafael J. Wysocki [this message]
2014-03-14 0:43 ` Ruchi Kandoi
2014-03-14 1:06 ` Rafael J. Wysocki
2014-03-14 2:15 ` Ruchi Kandoi
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=1559784.2mnpODc5zV@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--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®