| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-system-cpu | 122 Idle policy (governor) is differentiated from idle mechanism
131 switch the governor at runtime by writing to this file.
193 of a particular governor. In the ladder governor, for example,
|
| /openbmc/linux/drivers/watchdog/ |
| H A D | Kconfig | 101 tristate "Noop watchdog pretimeout governor"
105 Noop watchdog pretimeout governor, only an informational
109 tristate "Panic watchdog pretimeout governor"
113 Panic watchdog pretimeout governor, on watchdog pretimeout
120 This option selects a default watchdog pretimeout governor.
121 The governor takes its action, if a watchdog is capable
128 Use noop watchdog pretimeout governor by default. If noop
129 governor is selected by a user, write a short message to
136 Use panic watchdog pretimeout governor by default, if
164 bool "Software watchdog pretimeout governor support"
[all …]
|
| /openbmc/linux/drivers/cpuidle/ |
| H A D | cpuidle.c | 815 module_param_string(governor, param_governor, CPUIDLE_NAME_LEN, 0444);
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | kernel-per-CPU-kthreads.rst | 253 governor is not required, possibly enlisting the aid of
257 avoid the CPU-frequency governor periodically running
|
| H A D | kernel-parameters.txt | 833 cpuidle.governor=
834 [CPU_IDLE] Name of the cpuidle governor to use.
840 [CPU_FREQ] Name of the default cpufreq governor or
841 policy to use. This governor must be registered in the
2175 enabling its internal governor). This mode cannot be
|
| H A D | cgroup-v2.rst | 1021 cpufreq governor about the minimum desired frequency which should always be
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | sysfs-api.rst | 317 Name of the thermal governor used for this zone
344 |---policy: Thermal governor used for this zone
|
| /openbmc/linux/drivers/thermal/ |
| H A D | thermal_netlink.c | 543 tz->governor->name)) in thermal_genl_cmd_tz_get_gov()
|
| H A D | thermal_sysfs.c | 255 return sprintf(buf, "%s\n", tz->governor->name); in policy_show()
|
| /openbmc/linux/kernel/sched/ |
| H A D | cpufreq_schedutil.c | 857 if (old_gov == &schedutil_gov || policy->governor == &schedutil_gov) { in sched_cpufreq_governor_change()
|
| H A D | topology.c | 419 gov = policy->governor; in build_perf_domains()
|
| /openbmc/linux/drivers/cpufreq/ |
| H A D | amd-pstate.c | 551 max_perf, fast_switch, policy->governor->flags); in amd_pstate_update_freq()
613 policy->governor->flags); in amd_pstate_adjust_perf()
|
| /openbmc/linux/Documentation/power/ |
| H A D | energy-model.rst | 174 CPUfreq governor is in use in case of CPU device. Currently this calculation is
|
| /openbmc/linux/include/asm-generic/ |
| H A D | vmlinux.lds.h | 699 THERMAL_TABLE(governor) \
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 17 scheduler to make a better decision. And when schedutil cpufreq governor is
578 frequency of the cpufreq governor. It can be considered a more convenient
|
| H A D | sched-deadline.rst | 292 When cpufreq's schedutil governor is selected, SCHED_DEADLINE implements the
|
| /openbmc/linux/drivers/usb/gadget/ |
| H A D | Kconfig | 125 an CPU on-demand governor. Especially if DMA is doing IO to
|
| /openbmc/linux/arch/arm/boot/dts/nvidia/ |
| H A D | tegra20-asus-tf101.dts | 1215 * Ideally we should use userspace thermal governor,
|
| H A D | tegra30-asus-nexus7-grouper-common.dtsi | 1241 * Ideally we should use userspace thermal governor,
|
| H A D | tegra30-asus-transformer-common.dtsi | 1701 * Ideally we should use userspace thermal governor,
|
| H A D | tegra20-acer-a500-picasso.dts | 1447 * Ideally we should use userspace thermal governor,
|
| H A D | tegra30-pegatron-chagall.dts | 2782 * Ideally we should use userspace thermal governor,
|