Difference between revisions of "How to change the CPU frequency"

[quality revision] [checked revision]
m
 

1 Purpose[edit]

This article explains how to change the CPU operating point (also known as OPP). An operating point corresponds to the frequency of the processor and the voltage that needs to be supplied to sustain it.

2 Hardware side[edit]

On STM32MP1 Series products, the Cortex-A7 core is:

  • clocked by PLL1 from the RCC internal peripheral. The PLL1P output frequency can be directly propagated to the core, or it can go through an intermediate MPUDIV divider
  • supplied with VDDcore voltage.

The part number tells which devices can be clocked up to 800 MHz, with associated usage conditions. Otherwise, the frequency must be kept below 650 MHz.

3 Software side[edit]

3.1 For ecosystem release ≥ v1.2.0 More info.png[edit]

The ecosystem release ≥ v1.2.0 More info.png is backward compatible with the previous deliveries, so it is still possible to set the CPU frequency in the TF-A device tree, as described in the paragraph below. If your part number supports up to 800 MHz, ensure that the VDDcore minimum voltage is increased from 1.2V to 1.35 V while running above 650 MHz; this is done in the regulators node of the board device tree.

By default however, the ecosystem release ≥ v1.2.0 More info.png does not set any configuration for PLL1 in the FSBL (TF-A). Instead, TF-A automatically selects the operating point that is suitable for the current part number according to the OPP table code below (embedding frequency and voltage couples) defined in the SOC device tree fdts/stm32mp157c.dtsi .

	cpu0_opp_table: cpu0-opp-table {
		compatible = "operating-points-v2";
		opp-shared;

		opp-650000000 {
			opp-hz = /bits/ 64 <650000000>;
			opp-microvolt = <1200000>;
			opp-supported-hw = <0x1>;
		};
		opp-800000000 {
			opp-hz = /bits/ 64 <800000000>;
			opp-microvolt = <1350000>;
			opp-supported-hw = <0x2>;
		};
	};

Notes:

  • The operating point supported by devices supporting above 650 MHz (and up to 800 MHz) is identified by the opp-supported-hw property set to 0x2.
  • This same OPP table must also be present in the Linux SOC device tree arch/arm/boot/dts/stm32mp157c.dtsi .
  • It is possible to do a mix, specifying the PLL1 configuration (without an OPP table) in the TF-A device tree, whereas Linux uses the OPP table to increase the CPU frequency, once started.
  • This description is valid for cold boot, but also when coming back from Standby low power mode.
  • During cold boot, TF-A computes and saves the PLL1 settings for all operating points available in the device tree in compliance with the hardware capabilities. These saved paramaters are used later to increase the performance of the system-state transitions.

3.2 For ecosystem release ≤ v1.1.0 More info.png[edit]

The Cortex-A7 core frequency is selected at boot time, by the FSBL (TF-A), following the Clock device tree configuration - Bootloader specific syntax. The frequency is set to 650 MHz by default, as shown in STM32MP15 clock tree. This configuration is set in the TF-A device tree, for instance fdts/stm32mp157a-dk1.dts file for STM32MP157C-DK1 board.

&rcc {
	...
	/* VCO = 1300.0 MHz => P = 650 (CPU) */
	pll1: st,pll@0 {
		cfg = < 2 80 0 0 0 PQR(1,0,0) >;
		frac = < 0x800 >;
	};
	...
};

The user can reduce this frequency by changing the above configuration, either manually or via the STM32CubeMX graphical user interface that allows generation of the corresponding device tree file.


<noinclude>

{{ArticleMainWriter|OlivierB}}
{{ArticleApprovedVersion | Jean-ChristopheT | Nobody | No previous approved version | Automatic approval (article under construction) | 19Feb’19}}
[[==Purpose==
This article explains how to change the CPU '''operating point''' (also known as OPP). An operating point corresponds to the '''frequency''' of the processor and the  '''voltage''' that needs to be supplied to sustain it.

==Hardware side==
On {{MicroprocessorDevice | device=1}} products, the Cortex-A7 core is:
* clocked by PLL1 from the [[RCC internal peripheral]]. The PLL1P output '''frequency''' can be directly propagated to the core, or it can go through an intermediate MPUDIV divider
* supplied with VDDcore '''voltage'''.
The [[STM32MP15_microprocessor#Part_number_codification|part number]] tells which devices can be clocked up to 800 MHz, with associated usage conditions. Otherwise, the frequency must be kept below 650 MHz.

==Software side==
===For {{EcosystemRelease | revision=1.2.0 | range=and after}}===
The {{EcosystemRelease | revision=1.2.0 | range=and after}} is backward compatible with the previous deliveries, so it is still possible to set the CPU '''frequency''' in the TF-A device tree, as described in the paragraph below. If your [[STM32MP15_microprocessor#Part_number_codification|part number]] supports up to 800 MHz, ensure that the VDDcore minimum '''voltage''' is increased from 1.2V to 1.35 V while running above 650 MHz; this is done in the '''regulators''' node of the board device tree.<br>


By default however, the {{EcosystemRelease | revision=1.2.0 | range=and after}} does not set any configuration for PLL1 in the FSBL (TF-A). Instead, TF-A automatically selects the operating point that is suitable for the current [[STM32MP15_microprocessor#Part_number_codification|part number]] according to the OPP table code below (embedding '''frequency''' and '''voltage''' couples) defined in the SOC device tree {{CodeSource | TF-A | fdts/stm32mp157c.dtsi}}.<syntaxhighlight lang="c">

	cpu0_opp_table: cpu0-opp-table {
		compatible = "operating-points-v2";
		opp-shared;

		opp-650000000 {
			opp-hz = /bits/ 64 <650000000>;
			opp-microvolt = <1200000>;
			opp-supported-hw = <0x1>;
		};
		opp-800000000 {
			opp-hz = /bits/ 64 <800000000>;
			opp-microvolt = <1350000>;
			opp-supported-hw = <0x2>;
		};
	};</syntaxhighlight>

Notes:
* The operating point supported by devices supporting above 650 MHz (and up to 800 MHz) is identified by the '''opp-supported-hw''' property set to 0x2.
* This same OPP table must also be present in the Linux SOC device tree {{CodeSource | Linux kernel | arch/arm/boot/dts/stm32mp157c.dtsi}}.
* It is possible to do a mix, specifying the PLL1 configuration (without an OPP table) in the TF-A device tree, whereas Linux uses the OPP table to increase the CPU frequency, once started.
* This description is valid for cold boot, but also when coming back from [[Power overview|Standby]] low power mode.
* During cold boot, TF-A computes and saves the PLL1 settings for all operating points available in the device tree in compliance with the hardware capabilities. These saved paramaters are used later to increase the performance of the system-state transitions.

===For {{EcosystemRelease | revision=1.1.0 | range=and before}}===
The Cortex-A7 core frequency is selected at boot time, by the FSBL (TF-A), following the [[Clock device tree configuration - Bootloader specific]] syntax. The frequency is set to 650 MHz by default, as shown in [[STM32MP15 clock tree]]. This configuration is set in the TF-A device tree, for instance {{CodeSource | TF-A | fdts/stm32mp157a-dk1.dts}}  file for STM32MP157C-DK1 board.<br>
<syntaxhighlight lang="c">

&rcc {
	...
	/* VCO = 1300.0 MHz => P = 650 (CPU) */
	pll1: st,pll@0 {
		cfg = < 2 80 0 0 0 PQR(1,0,0) >;
		frac = < 0x800 >;
	};
	...
};</syntaxhighlight>

The user can reduce this frequency by changing the above configuration, either manually or via the  [[STM32CubeMX]] graphical user interface that allows generation of the corresponding device tree file.
<noinclude>

[[Category:How to customize software]]</noinclude>

{{UnderConstruction}}{{PublicationRequestId | 14900 | 2020-02-11 | AnneJ}}</noinclude>
(43 intermediate revisions by 7 users not shown)
Line 1: Line 1:
  +
==Purpose==
  +
This article explains how to change the CPU '''operating point''' (also known as OPP). An operating point corresponds to the '''frequency''' of the processor and the  '''voltage''' that needs to be supplied to sustain it.
  +
  +
==Hardware side==
  +
On {{MicroprocessorDevice | device=1}} products, the Cortex-A7 core is:
  +
* clocked by PLL1 from the [[RCC internal peripheral]]. The PLL1P output '''frequency''' can be directly propagated to the core, or it can go through an intermediate MPUDIV divider
  +
* supplied with VDDcore '''voltage'''.
  +
The [[STM32MP15_microprocessor#Part_number_codification|part number]] tells which devices can be clocked up to 800 MHz, with associated usage conditions. Otherwise, the frequency must be kept below 650 MHz.
  +
  +
==Software side==
  +
===For {{EcosystemRelease | revision=1.2.0 | range=and after}}===
  +
The {{EcosystemRelease | revision=1.2.0 | range=and after}} is backward compatible with the previous deliveries, so it is still possible to set the CPU '''frequency''' in the TF-A device tree, as described in the paragraph below. If your [[STM32MP15_microprocessor#Part_number_codification|part number]] supports up to 800 MHz, ensure that the VDDcore minimum '''voltage''' is increased from 1.2V to 1.35 V while running above 650 MHz; this is done in the '''regulators''' node of the board device tree.<br>
  +
  +
By default however, the {{EcosystemRelease | revision=1.2.0 | range=and after}} does not set any configuration for PLL1 in the FSBL (TF-A). Instead, TF-A automatically selects the operating point that is suitable for the current [[STM32MP15_microprocessor#Part_number_codification|part number]] according to the OPP table code below (embedding '''frequency''' and '''voltage''' couples) defined in the SOC device tree {{CodeSource | TF-A | fdts/stm32mp157c.dtsi}}.
  +
<syntaxhighlight lang="c">
  +
cpu0_opp_table: cpu0-opp-table {
  +
compatible = "operating-points-v2";
  +
opp-shared;
  +
  +
opp-650000000 {
  +
opp-hz = /bits/ 64 <650000000>;
  +
opp-microvolt = <1200000>;
  +
opp-supported-hw = <0x1>;
  +
};
  +
opp-800000000 {
  +
opp-hz = /bits/ 64 <800000000>;
  +
opp-microvolt = <1350000>;
  +
opp-supported-hw = <0x2>;
  +
};
  +
};
  +
</syntaxhighlight>
  +
Notes:
  +
* The operating point supported by devices supporting above 650 MHz (and up to 800 MHz) is identified by the '''opp-supported-hw''' property set to 0x2.
  +
* This same OPP table must also be present in the Linux SOC device tree {{CodeSource | Linux kernel | arch/arm/boot/dts/stm32mp157c.dtsi}}.
  +
* It is possible to do a mix, specifying the PLL1 configuration (without an OPP table) in the TF-A device tree, whereas Linux uses the OPP table to increase the CPU frequency, once started.
  +
* This description is valid for cold boot, but also when coming back from [[Power overview|Standby]] low power mode.
  +
* During cold boot, TF-A computes and saves the PLL1 settings for all operating points available in the device tree in compliance with the hardware capabilities. These saved paramaters are used later to increase the performance of the system-state transitions.
  +
  +
===For {{EcosystemRelease | revision=1.1.0 | range=and before}}===
  +
The Cortex-A7 core frequency is selected at boot time, by the FSBL (TF-A), following the [[Clock device tree configuration - Bootloader specific]] syntax. The frequency is set to 650 MHz by default, as shown in [[STM32MP15 clock tree]]. This configuration is set in the TF-A device tree, for instance {{CodeSource | TF-A | fdts/stm32mp157a-dk1.dts}}  file for STM32MP157C-DK1 board.<br>
  +
<syntaxhighlight lang="c">
  +
&rcc {
  +
...
  +
/* VCO = 1300.0 MHz => P = 650 (CPU) */
  +
pll1: st,pll@0 {
  +
cfg = < 2 80 0 0 0 PQR(1,0,0) >;
  +
frac = < 0x800 >;
  +
};
  +
...
  +
};
  +
</syntaxhighlight>
  +
The user can reduce this frequency by changing the above configuration, either manually or via the  [[STM32CubeMX]] graphical user interface that allows generation of the corresponding device tree file.
  +
 
<noinclude>
 
<noinclude>
{{ArticleMainWriter|OlivierB}}
 
{{ArticleApprovedVersion | Jean-ChristopheT | Nobody | No previous approved version | Automatic approval (article under construction) | 19Feb’19}}
 
 
[[Category:How to customize software]]
 
[[Category:How to customize software]]
  +
{{PublicationRequestId | 14900 | 2020-02-11 | AnneJ}}
 
</noinclude>
 
</noinclude>
{{UnderConstruction}}
 

Attachments

Discussions