From: Brian Norris <computersforpeace@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki\"" <rjw@rjwysocki.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] PM / sleep: add configurable delay for pm_test
Date: Thu, 4 Sep 2014 10:54:50 -0700 [thread overview]
Message-ID: <20140904175450.GB18411@ld-irv-0074> (raw)
In-Reply-To: <20140904071412.GA29832@amd>
On Thu, Sep 04, 2014 at 09:14:12AM +0200, Pavel Machek wrote:
> > When CONFIG_PM_DEBUG=y, we provide a sysfs file (/sys/power/pm_test) for
> > selecting one of a few suspend test modes, where rather than entering a
> > full suspend state, the kernel will perform some subset of suspend
> > steps, wait 5 seconds, and then resume back to normal operation.
> >
> > This mode is useful for (among other things) observing the state of the
> > system just before entering a sleep mode, for debugging or analysis
> > purposes. However, a constant 5 second wait is not sufficient for some
> > sorts of analysis; for example, on an SoC, one might want to use
> > external tools to probe the power states of various on-chip controllers
> > or clocks.
>
> When you are doing this kind of analysis, perhaps directly modifying
> kernel source is the way to go ...?
That's what I've been doing for now, but I have a few engineers who need
to do this sort of testing and aren't kernel developers. I could
continue to maintain my own patch for this, but I just thought I'd see
what others thought.
Is there a good reason this can't be in mainline? These features are
hidden behind a Kconfig symbol called PM_DEBUG anyway, and I think this
classifies as a pretty simple extension to the limited existing PM
debugging options.
Regards,
Brian
next prev parent reply other threads:[~2014-09-04 17:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 23:55 [PATCH] PM / sleep: add configurable delay for pm_test Brian Norris
[not found] ` <20140904071412.GA29832@amd>
2014-09-04 17:54 ` Brian Norris [this message]
2014-09-05 2:11 ` Chirantan Ekbote
2014-12-13 2:55 ` Brian Norris
2014-12-13 8:31 ` Pavel Machek
2014-12-16 23:58 ` Brian Norris
2014-12-17 8:09 ` Pavel Machek
2014-12-17 9:10 ` Brian Norris
2014-12-17 9:22 ` Pavel Machek
2015-02-21 20:25 ` Florian Fainelli
2015-02-21 20:32 ` Pavel Machek
2015-02-21 22:56 ` Florian Fainelli
2015-02-21 23:24 ` Pavel Machek
2015-02-22 8:23 ` Brian Norris
2015-02-22 8:26 ` [PATCH v2] " Brian Norris
2015-02-22 12:27 ` Pavel Machek
2015-02-22 15:17 ` Kevin Cernekee
2015-02-22 19:25 ` Florian Fainelli
2015-02-23 5:16 ` [PATCH v3] " Brian Norris
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=20140904175450.GB18411@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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