From: Ryan Underwood <nemesis@icequake.net>
To: cpufreq@lists.linux.org.uk
Subject: transition latency
Date: Thu, 28 Sep 2006 19:32:47 -0500 [thread overview]
Message-ID: <20060929003247.GA20765@dbz.icequake.net> (raw)
What's the purpose of the transition_latency field with respect to the
cpufreq infrastructure? Should I be setting this to:
* the time it takes for my set_cpu_state function to execute and return
* the latency between the call to set_cpu_state and the actual CPU speed
change
* the time it takes for the hardware to respond to MY request (inside
set_cpu_state function) to change speeds
Just a little confused. Here the problem is that my set_cpu_state
function could take up to 35ms to execute, but the actual frequency
transition ( a component of that function) happens within 7ms. 10ms is
the ondemand/conservative governors' upper limit for transition latency,
so if I take the whole function into account, those governors reject my
driver.
--
Ryan Underwood, <nemesis@icequake.net>
next reply other threads:[~2006-09-29 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 0:32 Ryan Underwood [this message]
2006-10-02 2:25 ` transition latency Dominik Brodowski
2006-10-02 5:07 ` Len Brown
2006-10-02 16:06 ` Ryan Underwood
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=20060929003247.GA20765@dbz.icequake.net \
--to=nemesis@icequake.net \
--cc=cpufreq@lists.linux.org.uk \
/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