Text of docs.kernel.org › cpu-freq › cpu-drivers.html as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

How to Implement a new CPUFreq Processor Driver — The Linux Kernel documentation

The Linux Kernel 7.4.0-rc3 Quick search Contents Working with the development community Development process Submitting patches Code of conduct Maintainer handbook All development-process docs Internal API manuals Core API Driver APIs Subsystems Core subsystems Human interfaces Networking interfaces Storage interfaces Other subsystems Accounting CPUFreq - CPU frequency and voltage scaling code in the Linux(TM) kernel EDAC Subsystem FPGA I2C/SMBus Subsystem Industrial I/O PCMCIA Serial Peripheral Interface (SPI) 1-Wire Subsystem Watchdog Support Virtualization Support Hardware Monitoring Compute Accelerators Security Documentation Crypto API BPF Documentation USB support PCI Bus Subsystem Assorted Miscellaneous Devices Documentation PECI Subsystem WMI Subsystem TEE Subsystem Locking Development tools and processes Licensing rules Writing documentation Development tools Testing guide Hacking guide Tracing Fault injection Livepatching Rust User-oriented documentation Administration Build system Reporting issues Userspace tools Userspace API Firmware-related documentation Firmware Firmware and Devicetree Architecture-specific documentation CPU architectures Other documentation Unsorted documentation Translations Translations This Page Show Source English Chinese (Simplified) Chinese (Traditional) How to Implement a new CPUFreq Processor Driver ¶ Authors: Dominik Brodowski < linux @ brodo . de > Rafael J.

Wysocki < rafael . j . wysocki @ intel . com > Viresh Kumar < viresh . kumar @ linaro . org > 1. What To Do? ¶ So, you just got a brand-new CPU / chipset with datasheets and want to add cpufreq support for this CPU / chipset? Great. Here are some hints on what is necessary: 1.1 Initialization ¶ First of all, in an __initcall level 7 ( module_init() ) or later function check whether this kernel runs on the right CPU and the right chipset.

If so, register a struct cpufreq_driver with the CPUfreq core using cpufreq_register_driver() What shall this struct cpufreq_driver contain? .name - The name of this driver. .init - A pointer to the per-policy initialization function. .verify - A pointer to a “verification” function. .setpolicy _or_ .fast_switch _or_ .target _or_ .target_index - See below on the differences. And optionally .flags - Hints for the cpufreq core. .driver_data - cpufreq driver specific data. .get_intermediate and target_intermediate - Used to switch to stable frequency while changing CPU frequency. .get - Returns current frequency of the CPU. .bios_limit - Returns HW/BIOS max frequency limitations for the CPU. .exit - A pointer to a per-policy cleanup function called during CPU_POST_DEAD phase of cpu hotplug process. .suspend - A pointer to a per-policy suspend function which is called with interrupts disabled and _after_ the governor is stopped for the policy. .resume - A pointer to a per-policy resume function which is called with interrupts disabled and _before_ the governor is started again. .ready - A pointer to a per-policy ready function which is called after the policy is fully initialized. .attr - A pointer to a NULL-terminated list of “ struct freq_attr ” which allow to export values to sysfs. .boost_enabled - If set, boost frequencies are enabled. .set_boost - A pointer to a per-policy function to enable/disable boost frequencies.

1.2 Per-CPU Initialization ¶ Whenever a new CPU is registered with the device model, or after the cpufreq driver registers itself, the per-policy initialization function cpufreq_driver.init is called if no cpufreq policy existed for the CPU. Note that the . init() and . exit() routines are called only once for the policy and not for each CPU managed by the policy. It takes a struct cpufreq_policy *policy as argument.

What to do now? If necessary, activate the CPUfreq support on your CPU. Then, the driver must fill in the following values: policy->cpuinfo.min_freq _and_ policy->cpuinfo.max_freq the minimum and maximum frequency (in kHz) which is supported by this CPU policy->cpuinfo.transition_latency the time it takes on this CPU to switch between two frequencies in nanoseconds policy->cur The current operating frequency of this CPU (if appropriate) policy->min, policy->max The min/max scaling frequency.

If set by the driver in -> init() , used as the lower/upper bound for policy frequency QoS requests; otherwise, reflects the min/max frequency the driver can set policy->policy and, if necessary, policy->governor must contain the “default policy” for this CPU. A few moments later, cpufreq_driver.verify and either cpufreq_driver.setpolicy or cpufreq_driver.target/target_index is called with these values. policy->cpus Update this with the masks of the (online + offline) CPUs that do DVFS along with this CPU (i.e. that share clock/voltage rails with it).

For setting some of these values (cpuinfo.min[max]_freq, policy->min[max]), the frequency table helpers might be helpful. See the section 2 for more information on them. 1.3 verify ¶ When the user decides a new policy (consisting of “policy,governor,min,max”) shall be set, this policy must be validated so that incompatible values can be corrected. For verifying these values cpufreq_verify_within_limits( struct cpufreq_policy *policy , unsigned int min_freq , unsigned int max_freq ) function might be helpful.

See section 2 for details on frequency table helpers. You need to make sure that at least one valid frequency (or operating range) is within policy->min and policy->max. If necessary, increase policy->max first, and only if this is no solution, decrease policy->min. 1.4 target or target_index or setpolicy or fast_switch? ¶ Most cpufreq drivers or even most cpu frequency scaling algorithms only allow the CPU frequency to be set to predefined fixed values.

For these, you use the -> target() , -> target_index() or -> fast_switch() callbacks. Some cpufreq capable processors switch the frequency between certain limits on their own. These shall use the -> setpolicy() callback. 1.5. target/target_index ¶ The target_index call has two arguments: struct cpufreq_policy *policy , and unsigned int index (into the exposed frequency table). The CPUfreq driver must set the new frequency when called here.

The actual frequency must be determined by freq_table[index].frequency. It should always restore to earlier frequency (i.e. policy->restore_freq) in case of errors, even if we switched to intermediate frequency earlier. Deprecated ¶ The target call has three arguments: struct cpufreq_policy *policy , unsigned int target_frequency, unsigned int relation. The CPUfreq driver must set the new frequency when called here. The actual frequency must be determined using the following rules: keep close to “target_freq” policy->min <= new_freq <= policy->max (THIS MUST BE VALID!!!) if relation==CPUFREQ_REL_L, try to select a new_freq higher than or equal target_freq. (“L for lowest, but no lower than”) if relation==CPUFREQ_REL_H, try to select a new_freq lower than or equal target_freq. (“H for highest, but no higher than”) Here again the frequency table helper might assist you - see section 2 for details.

1.6. fast_switch ¶ This function is used for frequency switching from scheduler’s context. Not all drivers are expected to implement it, as sleeping from within this callback isn’t allowed. This callback must be highly optimized to do switching as fast as possible. This function has two arguments: struct cpufreq_policy *policy and unsigned int target_frequency . 1.7 setpolicy ¶ The setpolicy call only takes a struct cpufreq_policy *policy as argument.

You need to set the lower limit of the in-processor or in-chipset dynamic frequency switching to policy->min, the upper limit to policy->max, and -if supported- select a performance-oriented setting when policy->policy is CPUFREQ_POLICY_PERFORMANCE, and a powersaving-oriented setting when CPUFREQ_POLICY_POWERSAVE. Also check the reference implementation in drivers/cpufreq/longrun.c 1.8 ge

The rest of this page is on the live site.