From: manty kuma <mantykuma@gmail.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: linux-omap@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
linux-embedded@vger.kernel.org, Ran Shalit <ranshalit@gmail.com>,
linux-pm@vger.kernel.org
Subject: Re: cpuidle - minimum time for sleep
Date: Fri, 10 Oct 2014 12:22:55 +0900 [thread overview]
Message-ID: <CAB6A5-BJZtcT0GZpYC=TOeXrEC+mvTCxKkVftObxzt3OkNadHQ@mail.gmail.com> (raw)
In-Reply-To: <11792.1412881303@turing-police.cc.vt.edu>
[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]
>> Does anybody know what is the minimum expected time for sleep period
>> with the cpuidle ?
By sleep period do you mean sleep time for complete device or only for
cpu's? If you want to check for device as a whole, you can see the print in
the kernel log. If you want to check programmatically,
suspend_devices_and_enter() is the function.
On Fri, Oct 10, 2014 at 4:01 AM, <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
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
[-- Attachment #1.2: Type: text/html, Size: 1499 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2014-10-10 3:22 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
2014-10-10 3:22 ` manty kuma [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='CAB6A5-BJZtcT0GZpYC=TOeXrEC+mvTCxKkVftObxzt3OkNadHQ@mail.gmail.com' \
--to=mantykuma@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).