linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Valdis.Kletnieks@vt.edu, Ran Shalit <ranshalit@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>,
	linux-pm@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-embedded@vger.kernel.org
Subject: Re: cpuidle - minimum time for sleep
Date: Thu, 9 Oct 2014 14:20:39 -0500	[thread overview]
Message-ID: <5436E007.7000909@ti.com> (raw)
In-Reply-To: <11792.1412881303@turing-police.cc.vt.edu>

On 10/09/2014 02:01 PM, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 09 Oct 2014 21:28:23 +0300, Ran Shalit said:
> 
>> Does anybody know what is the minimum expected time for sleep period
>> with the cpuidle ?
> 
> Both processor dependent and sleep level dependent.  There's a certain
> amount of latency induced by the hardware waking up.
> 
> Look at /sys/devices/system/cpu/cpu*/cpuidle/state*/latency
> 
Yes, that is correct. the sleep and wakeup time are dependent on the
power state we attempt (may or maynot achieve)

I personally toggle an unused pin using padmux register write with
weak pull up/down in controlled tests (mostly using disable =1 for
states I am not measuring), then capture pinctrl toggles using [1]
into a csv for many thousands of iterations then use the conservative
values. I usually do this at the slowest frequency to capture the
worst case values that i feed into cpuidle_driver.states.exit_latency
and appropriate value for target_residency - I usually ignore
power_usage as the value is never a constant and depends on quiet a
few factors that i cannot discuss in public domain.

Here are some helpful links on OMAP specific strategies (these may be
a little old, but just search for CPUIDLE latency measure in google)

https://lwn.net/Articles/384146/

http://www.omappedia.org/wiki/Power_Management_Device_Latencies_Measurement

http://lists.linaro.org/pipermail/linaro-dev/2010-August/000568.html


[1] https://www.saleae.com/

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2014-10-09 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 18:28 cpuidle - minimum time for sleep Ran Shalit
2014-10-09 19:01 ` Valdis.Kletnieks
2014-10-09 19:20   ` Nishanth Menon [this message]
2014-10-10  3:22   ` manty kuma

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=5436E007.7000909@ti.com \
    --to=nm@ti.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ranshalit@gmail.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;
as well as URLs for NNTP newsgroup(s).