The policy already has this pointer set, use it instead.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpu-drivers.txt | 1 -
drivers/cpufreq/amd_freq_sensitivity.c | 3 +--
drivers/cpufreq/cpufreq.c | 4 ++--
drivers/cpufreq/cpufreq_onde
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 <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpu-drivers.tx
The policy already has this pointer set, use it instead.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpu-drivers.txt | 1 -
drivers/cpufreq/amd_freq_sensitivity.c | 3 +--
drivers/cpufreq/cpufreq.c | 4 ++--
drivers/cpufreq/cpufreq_onde
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 <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpu-drivers.tx
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 <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpu-drivers.tx
The policy already has this pointer set, use it instead.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpu-drivers.txt | 1 -
drivers/cpufreq/amd_freq_sensitivity.c | 3 +--
drivers/cpufreq/cpufreq.c | 4 ++--
drivers/cpufreq/cpufreq_onde
ing its ``->start()`` callback.
The rest of it looked good. Nice work Rafael :)
Acked-by: Viresh Kumar <viresh.ku...@linaro.org>
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 20-02-17, 14:58, Rafael J. Wysocki wrote:
> Yes, it is called for new and inactive policies.
>
> For new policies it has to populate policy->cpus (because otherwise the core
> doesn't know what CPUs should be there), which quite arguably doesn't have
> to (or even doesn't need to) be done for
Signed-off-by: Todd Poynor <toddpoy...@google.com>
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/governors.txt | 86 ++
drivers/cpufreq/Kconfig| 30 +
drivers/cpufreq/Makefile |1 +
drivers/cpufreq/cpu
On 09-09-16, 13:03, Jean Delvare wrote:
> On Fri, 9 Sep 2016 00:38:59 +0200, Rafael J. Wysocki wrote:
> > On 9/8/2016 1:20 PM, Viresh Kumar wrote:
> > > On 08-09-16, 12:39, Jean Delvare wrote:
> > >> The cpufreq-stats code can no longer be built as a module, so it
On 27-10-16, 18:41, Patrick Bellasi wrote:
> +This last requirement is especially important if we consider that schedutil
> can
> +potentially replace all currently available CPUFreq policies. Since schedutil
> +is event based, as opposed to the sampling driven governors, it is already
> more
>
quot; notebooks are supported.
> -
> +The following POWER processors are supported in powernv mode:
> +POWER8
> +POWER9
>
> 1.5 SuperH
> --
Acked-by: Viresh Kumar <viresh.ku...@linaro.org>
--
viresh
--
To unsubscribe from this list: send the line "unsub
This patch doesn't change the content of the documentation, but rather
reformat it to make it more readable.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/governors.txt | 205 +++
1 file changed, 112 insertions(+), 93 del
quot; after boot_constraints_disable kernel param.
- Dropped the dummy testing patch now.
--
viresh
[1] https://marc.info/?l=dri-devel=149979722606563=2
Rajendra Nayak (1):
drivers: boot_constraint: Add Qualcomm display controller constraints
Viresh Kumar (7):
drivers: Add boot constraints cor
the constraint.
We can also think about finer control of such constraints with help of
some sysfs files, but a kernel parameter is fine to begin with.
Tested-by: Rajendra Nayak <rna...@codeaurora.org>
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/admin-guide/kernel-pa
the constraint.
We can also think about finer control of such constraints with help of
some sysfs files, but a kernel parameter is fine to begin with.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/admin-guide/kernel-parameters.txt | 3 +++
drivers/base/boot_constr
nik for his feedback on
that.
--
viresh
Viresh Kumar (6):
cpufreq: Replace "max_transition_latency" with "dynamic_switching"
cpufreq: schedutil: Set dynamic_switching to true
cpufreq: governor: Drop min_sampling_rate
cpufreq: Use transition_delay_us for legacy governors
be changed and then one of the CPUs in
the policy will be only changing frequency for ever.
But that is something for the user to decide and there is no need to
have special handling for such cases in the core. Leave it for the user
to figure out.
Signed-off-by: Viresh Kumar <viresh
from
> + the hardware (in KHz).
> +
> + This is expected to be the frequency the hardware actually runs at.
> + If that frequency cannot be determined, this attribute should not
> + be present.
> +
> ``cpuinfo_max_freq``
> Maximum possible operating
where the
transition latency set to CPUFREQ_ETERNAL would not allow use of
ondemand/conservative governors. Thanks to Dominik for his feedback on
that.
--
viresh
Viresh Kumar (9):
cpufreq: governor: Drop min_sampling_rate
cpufreq: Use transition_delay_us for legacy governors as well
cpufre
be changed and then one of the CPUs in
the policy will be only changing frequency for ever.
But that is something for the user to decide and there is no need to
have special handling for such cases in the core. Leave it for the user
to figure out.
Signed-off-by: Viresh Kumar <viresh
On 30-06-17, 06:53, Dominik Brodowski wrote:
> On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote:
> > On 29-06-17, 20:01, Dominik Brodowski wrote:
> > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote:
> > > > The cpufreq core and governors
On 29-06-17, 20:01, Dominik Brodowski wrote:
> On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote:
> > The cpufreq core and governors aren't supposed to set a limit on how
> > fast we want to try changing the frequency. This is currently done for
> > the legac
the constraint.
We can also think about finer control of such constraints with help of
some sysfs files, but a kernel parameter is fine to begin with.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/admin-guide/kernel-parameters.txt | 2 ++
drivers/base/boot_constr
be changed and then one of the CPUs in
the policy will be only changing frequency for ever.
But that is something for the user to decide and there is no need to
have special handling for such cases in the core. Leave it for the user
to figure out.
Signed-off-by: Viresh Kumar <viresh
m/Documentation/cpu-freq/index.txt
> @@ -32,8 +32,6 @@ cpufreq-stats.txt - General description
>
> index.txt - File index, Mailing list and Links (this document)
>
> -intel-pstate.txt - Intel pstate cpufreq driver specific file.
> -
> pcc-cpufreq.
On 29-08-17, 08:37, Greg Kroah-Hartman wrote:
> On Tue, Aug 01, 2017 at 02:53:43PM +0530, Viresh Kumar wrote:
> > + boot_constraints_disable
> > + Do not set any boot constraints for devices.
>
> Shouldn't that be the default? As really, that is what the
It isn't used by anyone, drop it.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/thermal/cpu-cooling-api.txt | 24 +++-
drivers/thermal/cpu_cooling.c | 30 --
include/linux/cpu_cooling.h
All the callers of of_cpufreq_power_cooling_register() have almost
identical code and it makes more sense to move that code into the helper
as its all about reading DT properties.
This got rid of lot of redundant code.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documen
() and
rename of_cpufreq_power_cooling_register() as
of_cpufreq_cooling_register(). This simplifies lots of stuff.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/thermal/cpu-cooling-api.txt | 14 ++--
drivers/cpufreq/arm_big_little.c | 2 +-
drivers/c
atus
/sys/class/thermal/cooling_device0/stats:
reset time_in_state total_trans trans_table
This is tested on ARM 64-bit Hisilicon hikey620 board running Ubuntu and
ARM 64-bit Hisilicon hikey960 board running Android.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
V3->V4:
- A
commit 84fe2cab4859 ("cpu_cooling: Drop static-power related stuff")
removed support for static-power in kernel, but it missed reflecting the
same in documentation. Remove the static power related documentation
bits as well.
Reported-by: Javi Merino <javi.mer...@kernel.org>
Signe
On 16-01-18, 15:22, Viresh Kumar wrote:
> This extends the sysfs interface for thermal cooling devices and exposes
> some pretty useful statistics. These statistics have proven to be quite
> useful specially while doing benchmarks related to the task scheduler,
> where we want
On 13-03-18, 15:02, Zhang Rui wrote:
> Hi, Viresh,
>
> I will queue it for 4.17, with just one minor fix below.
>
> On 二, 2018-01-16 at 15:22 +0530, Viresh Kumar wrote:
> > + cdev->stats = stats;
> > + stats->last_time = ktime_get();
> > + stats-&g
On 14-03-18, 16:01, Zhang Rui wrote:
> WARNING: please write a paragraph that describes the config symbol
> fully
> #147: FILE: drivers/thermal/Kconfig:18:
> +config THERMAL_STATISTICS
>
> WARNING: Consider renaming function(s)
> 'thermal_cooling_device_total_trans_show' to 'total_trans_show'
>
atus
/sys/class/thermal/cooling_device0/stats:
reset time_in_state_ms total_trans trans_table
This is tested on ARM 64-bit Hisilicon hikey620 board running Ubuntu and
ARM 64-bit Hisilicon hikey960 board running Android.
Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
V4->V5
On 28-03-18, 22:59, Sanjeev Gupta wrote:
> All links working.
And why is it important to convert them to https ?
> Signed-off-by: Sanjeev Gupta
> ---
> Documentation/thermal/cpu-cooling-api.txt | 2 +-
> Documentation/thermal/nouveau_thermal | 2 +-
> 2 files changed, 2
On 14-03-18, 13:44, Viresh Kumar wrote:
> I got those warnings as well, and I quietly ignored them :)
>
> I ignored the renaming part for the sake of consistency. The other existing
> routines for similar purpose are named as:
>
> thermal_coolin
38 matches
Mail list logo