| .. | .. |
|---|
| 443 | 443 | (u32) cpu->acpi_perf_data.states[i].control); |
|---|
| 444 | 444 | } |
|---|
| 445 | 445 | |
|---|
| 446 | | - /* |
|---|
| 447 | | - * The _PSS table doesn't contain whole turbo frequency range. |
|---|
| 448 | | - * This just contains +1 MHZ above the max non turbo frequency, |
|---|
| 449 | | - * with control value corresponding to max turbo ratio. But |
|---|
| 450 | | - * when cpufreq set policy is called, it will call with this |
|---|
| 451 | | - * max frequency, which will cause a reduced performance as |
|---|
| 452 | | - * this driver uses real max turbo frequency as the max |
|---|
| 453 | | - * frequency. So correct this frequency in _PSS table to |
|---|
| 454 | | - * correct max turbo frequency based on the turbo state. |
|---|
| 455 | | - * Also need to convert to MHz as _PSS freq is in MHz. |
|---|
| 456 | | - */ |
|---|
| 457 | | - if (!global.turbo_disabled) |
|---|
| 458 | | - cpu->acpi_perf_data.states[0].core_frequency = |
|---|
| 459 | | - policy->cpuinfo.max_freq / 1000; |
|---|
| 460 | 446 | cpu->valid_pss_table = true; |
|---|
| 461 | 447 | pr_debug("_PPC limits will be enforced\n"); |
|---|
| 462 | 448 | |
|---|
| .. | .. |
|---|
| 777 | 763 | err = cpufreq_start_governor(policy); |
|---|
| 778 | 764 | if (!ret) |
|---|
| 779 | 765 | ret = err; |
|---|
| 766 | + } else { |
|---|
| 767 | + ret = 0; |
|---|
| 780 | 768 | } |
|---|
| 781 | 769 | } |
|---|
| 782 | 770 | |
|---|