linux.git/Documentation/cpu-freq, branch v4.10

Documentation: intel_pstate: Document HWP energy/performance hints

2016-12-08T00:43:05+00:00

Updated documentation for the support of energy performance hint in
the HWP mode.

Signed-off-by: Srinivas Pandruvada 
[ rjw: Subject & changelog ]
Signed-off-by: Rafael J. Wysocki

cpufreq: stats: New sysfs attribute for clearing statistics

2016-11-11T00:51:11+00:00

Allow CPUfreq statistics to be cleared by writing anything to
/sys/.../cpufreq/stats/reset.

Signed-off-by: Markus Mayer 
Acked-by: Viresh Kumar 
Signed-off-by: Rafael J. Wysocki

Documentation: intel_pstate: Update per core limits

2016-11-01T05:04:06+00:00

Document restriction on per core P-State control.

Signed-off-by: Srinivas Pandruvada 
Signed-off-by: Rafael J. Wysocki

Documentation: intel_pstate: PID tuning is not always available

2016-10-21T20:17:32+00:00

PID tuning is not available when the get_target_pstate_use_cpu_load()
is used to calculate target_state. So update the documentation.

Signed-off-by: Srinivas Pandruvada 
Signed-off-by: Rafael J. Wysocki

cpufreq-stats: Minor documentation fix

2016-09-08T21:05:07+00:00

The cpufreq-stats code can no longer be built as a module, so it now
appears with square brackets in menuconfig.

Signed-off-by: Jean Delvare 
Fixes: 1aefc75b2449 (cpufreq: stats: Make the stats code non-modular)
Acked-by: Viresh Kumar 
Signed-off-by: Rafael J. Wysocki

Revert "cpufreq: pcc-cpufreq: update default value of cpuinfo_transition_latency"

2016-07-22T21:51:06+00:00

This reverts commit 790d849bf811a8ab5d4cd2cce0f6fda92f6aebf2.

Using a v4.7-rc7 kernel on a HP ProLiant triggered following messages

 pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2800 MHz
 cpufreq: ondemand governor failed, too long transition latency of HW, fallback to performance governor

The last line was shown for each CPU in the system.
Testing v4.5 (where commit 790d849b was integrated) triggered
similar messages. Same behaviour on a 2nd HP Proliant system.

So commit 790d849bf (cpufreq: pcc-cpufreq: update default value of
cpuinfo_transition_latency) causes the system to use performance
governor which, I guess, was not the intention of the patch.

Enabling debug output in pcc-cpufreq provides following verbose output:

 pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2800 MHz
 pcc_get_offset: for CPU 0: pcc_cpu_data input_offset: 0x44, pcc_cpu_data output_offset: 0x48
 init: policy->max is 2800000, policy->min is 1200000
 get: get_freq for CPU 0
 get: SUCCESS: (virtual) output_offset for cpu 0 is 0xffffc9000d7c0048, contains a value of: 0xff06. Speed is: 168000 MHz
 cpufreq: ondemand governor failed, too long transition latency of HW, fallback to performance governor
 target: CPU 0 should go to target freq: 2800000 (virtual) input_offset is 0xffffc9000d7c0044
 target: was SUCCESSFUL for cpu 0

I am asking to revert 790d849bf to re-enable usage of ondemand
governor with pcc-cpufreq.

Fixes: 790d849bf (cpufreq: pcc-cpufreq: update default value of cpuinfo_transition_latency)
CC:  # 4.5+
Signed-off-by: Andreas Herrmann 
Signed-off-by: Rafael J. Wysocki

cpufreq: Return index from cpufreq_frequency_table_target()

2016-06-08T22:58:06+00:00

This routine can't fail unless the frequency table is invalid and
doesn't contain any valid entries.

Make it return the index and WARN() in case it is used for an invalid
table.

Signed-off-by: Viresh Kumar 
Signed-off-by: Rafael J. Wysocki

cpufreq: Drop freq-table param to cpufreq_frequency_table_target()

2016-06-08T22:58:06+00:00

The policy already has this pointer set, use it instead.

Signed-off-by: Viresh Kumar 
Signed-off-by: Rafael J. Wysocki

cpufreq: Unexport cpufreq_frequency_table_cpuinfo()

2016-06-02T21:24:41+00:00

All cpufreq drivers with a freq-table are migrated to use
cpufreq_table_validate_and_show() long back and the routine
cpufreq_frequency_table_cpuinfo() isn't used outside of cpufreq core
now.

Unexport it and update Documentation as well.

Signed-off-by: Viresh Kumar 
Signed-off-by: Rafael J. Wysocki

Documentation: cpufreq: intel_pstate: fix typo

2016-02-18T19:31:53+00:00

This just swaps a colon for a quote in the intel_pstate documentation.

Signed-off-by: Felipe Franciosi 
Signed-off-by: Rafael J. Wysocki