.TH "CPUPOWER\-FREQUENCY\-INFO" "1" "0.1" "" "cpupower Manual"
.SH "NAME"
.LP 
cpupower\-frequency\-info \- Utility to retrieve cpufreq kernel information
.SH "SYNTAX"
.LP 
cpupower [ \-c cpulist ] frequency\-info [\fIoptions\fP]
.SH "DESCRIPTION"
.LP 
A small tool which prints out cpufreq information helpful to developers and interested users.
.SH "OPTIONS"
.LP 
.TP  
\fB\-e\fR \fB\-\-debug\fR
Prints out debug information.
.TP  
\fB\-f\fR \fB\-\-freq\fR
Get frequency the CPU currently runs at, according to the cpufreq core.
.TP  
\fB\-w\fR \fB\-\-hwfreq\fR
Get frequency the CPU currently runs at, by reading it from hardware (only available to root).
.TP  
\fB\-l\fR \fB\-\-hwlimits\fR
Determine the minimum and maximum CPU frequency allowed.
.TP  
\fB\-d\fR \fB\-\-driver\fR
Determines the used cpufreq kernel driver.
.TP  
\fB\-p\fR \fB\-\-policy\fR
Gets the currently used cpufreq policy.
.TP  
\fB\-g\fR \fB\-\-governors\fR
Determines available cpufreq governors.
.TP  
\fB\-a\fR \fB\-\-related\-cpus\fR
Determines which CPUs run at the same hardware frequency.
.TP  
\fB\-a\fR \fB\-\-affected\-cpus\fR
Determines which CPUs need to have their frequency coordinated by software.
.TP  
\fB\-s\fR \fB\-\-stats\fR
Shows cpufreq statistics if available.
.TP  
\fB\-y\fR \fB\-\-latency\fR
Determines the maximum latency on CPU frequency changes.
.TP  
\fB\-o\fR \fB\-\-proc\fR
Prints out information like provided by the /proc/cpufreq interface in 2.4. and early 2.6. kernels.
.TP  
\fB\-m\fR \fB\-\-human\fR
human\-readable output for the \-f, \-w, \-s and \-y parameters.
.TP  
\fB\-n\fR \fB\-\-no-rounding\fR
Output frequencies and latencies without rounding off values.
.TP  
.SH "REMARKS"
.LP 
By default only values of core zero are displayed. How to display settings of
other cores is described in the cpupower(1) manpage in the \-\-cpu option section.
.LP 
You can't specify more than one of the output specific options \-o \-e \-a \-g \-p \-d \-l \-w \-f \-y.
.LP 
You also can't specify the \-o option combined with the \-c option.
.SH "FILES"
.nf 
\fI/sys/devices/system/cpu/cpu*/cpufreq/\fP  
\fI/proc/cpufreq\fP (deprecated) 
\fI/proc/sys/cpu/\fP (deprecated)
.fi 
.SH "AUTHORS"
.nf
Dominik Brodowski <linux@brodo.de> \- author 
Mattia Dongili<malattia@gmail.com> \- first autolibtoolization
.fi
.SH "SEE ALSO"
.LP 
cpupower\-frequency\-set(1), cpupower(1)

<option value='committer'>committer</option>
<option value='range'>range</option>
</select>
<input class='txt' type='search' size='10' name='q' value=''/>
<input type='submit' value='search'/>
</form>
</td></tr></table>
<div class='path'>path: <a href='/cgit.cgi/linux/net-next.git/commit/?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>root</a>/<a href='/cgit.cgi/linux/net-next.git/commit/sound?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>sound</a>/<a href='/cgit.cgi/linux/net-next.git/commit/sound/mips?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>mips</a>/<a href='/cgit.cgi/linux/net-next.git/commit/sound/mips/ad1843.c?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>ad1843.c</a></div><div class='content'><div class='cgit-panel'><b>diff options</b><form method='get'><input type='hidden' name='id' value='4205e4786d0b9fc3b4fec7b1910cf645a0468307'/><table><tr><td colspan='2'/></tr><tr><td class='label'>context:</td><td class='ctrl'><select name='context' onchange='this.form.submit();'><option value='1'>1</option><option value='2'>2</option><option value='3' selected='selected'>3</option><option value='4'>4</option><option value='5'>5</option><option value='6'>6</option><option value='7'>7</option><option value='8'>8</option><option value='9'>9</option><option value='10'>10</option><option value='15'>15</option><option value='20'>20</option><option value='25'>25</option><option value='30'>30</option><option value='35'>35</option><option value='40'>40</option></select></td></tr><tr><td class='label'>space:</td><td class='ctrl'><select name='ignorews' onchange='this.form.submit();'><option value='0' selected='selected'>include</option><option value='1'>ignore</option></select></td></tr><tr><td class='label'>mode:</td><td class='ctrl'><select name='dt' onchange='this.form.submit();'><option value='0' selected='selected'>unified</option><option value='1'>ssdiff</option><option value='2'>stat only</option></select></td></tr><tr><td/><td class='ctrl'><noscript><input type='submit' value='reload'/></noscript></td></tr></table></form></div><table summary='commit info' class='commit-info'>
<tr><th>author</th><td>Thomas Gleixner &lt;tglx@linutronix.de&gt;</td><td class='right'>2017-01-10 14:01:05 +0100</td></tr>
<tr><th>committer</th><td>Thomas Gleixner &lt;tglx@linutronix.de&gt;</td><td class='right'>2017-01-16 13:20:05 +0100</td></tr>
<tr><th>commit</th><td colspan='2' class='oid'><a href='/cgit.cgi/linux/net-next.git/commit/sound/mips/ad1843.c?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>4205e4786d0b9fc3b4fec7b1910cf645a0468307</a> (<a href='/cgit.cgi/linux/net-next.git/patch/sound/mips/ad1843.c?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>patch</a>)</td></tr>
<tr><th>tree</th><td colspan='2' class='oid'><a href='/cgit.cgi/linux/net-next.git/tree/?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>685ccb486409197b936c785eb9d173c3edff45a1</a> /<a href='/cgit.cgi/linux/net-next.git/tree/sound/mips/ad1843.c?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>sound/mips/ad1843.c</a></td></tr>
<tr><th>parent</th><td colspan='2' class='oid'><a href='/cgit.cgi/linux/net-next.git/commit/sound/mips/ad1843.c?id=7e164ce4e8ecd7e9a58a83750bd3ee03125df154'>7e164ce4e8ecd7e9a58a83750bd3ee03125df154</a> (<a href='/cgit.cgi/linux/net-next.git/diff/sound/mips/ad1843.c?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307&amp;id2=7e164ce4e8ecd7e9a58a83750bd3ee03125df154'>diff</a>)</td></tr></table>
<div class='commit-subject'>cpu/hotplug: Provide dynamic range for prepare stage</div><div class='commit-msg'>Mathieu reported that the LTTNG modules are broken as of 4.10-rc1 due to
the removal of the cpu hotplug notifiers.

Usually I don't care much about out of tree modules, but LTTNG is widely
used in distros. There are two ways to solve that:

1) Reserve a hotplug state for LTTNG

2) Add a dynamic range for the prepare states.

While #1 is the simplest solution, #2 is the proper one as we can convert
in tree users, which do not care about ordering, to the dynamic range as
well.

Add a dynamic range which allows LTTNG to request states in the prepare
stage.

Reported-and-tested-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Reviewed-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;
Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;
Cc: Sebastian Sewior &lt;bigeasy@linutronix.de&gt;
Cc: Steven Rostedt &lt;rostedt@goodmis.org&gt;
Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701101353010.3401@nanos
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;

</div><div class='diffstat-header'><a href='/cgit.cgi/linux/net-next.git/diff/?id=4205e4786d0b9fc3b4fec7b1910cf645a0468307'>Diffstat</a> (limited to 'sound/mips/ad1843.c')</div><table summary='diffstat' class='diffstat'>