| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | intel_pstate.rst | 30 uses frequencies for identifying operating performance points of CPUs and
31 frequencies are involved in the user space interface exposed by it, so
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
35 available frequencies due to the possible size of it, so the driver does not do
221 maximum and minimum operating frequencies supported by the hardware (including
318 of P-states into frequencies and the other way around.
613 available frequencies supplied by ``acpi-cpufreq`` to the ``CPUFreq`` core and
614 scaling governors and the minimum and maximum supported frequencies reported by
629 benefit from running at turbo frequencies will be given non-turbo P-states
|
| H A D | cpufreq_drivers.rst | 197 frequencies supported by the platform firmware.
223 frequencies need to be listed because the BIOS will try to achieve any
|
| H A D | intel_uncore_frequency_scaling.rst | 22 the scaling min/max frequencies via cpufreq sysfs to improve CPU performance.
|
| /openbmc/linux/Documentation/devicetree/bindings/thermal/ |
| H A D | thermal-cooling-devices.yaml | 30 scaling (DVFS), and uses lower frequencies as cooling states.
|
| H A D | nvidia,tegra124-soctherm.yaml | 94 of pulse skippers, which used to throttle clock frequencies. It
111 frequencies. It indicates gpu clock throttling depth and can be
|
| /openbmc/linux/arch/arm64/boot/dts/marvell/ |
| H A D | cn9131-db.dtsi | 145 /* On-board MUX does not allow higher frequencies */
|
| H A D | cn9130-crb.dtsi | 183 /* On-board MUX does not allow higher frequencies */
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | video-interfaces.yaml | 191 link-frequencies:
194 Allowed data bus frequencies. For MIPI CSI-2, for instance, this is the
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | mvebu-core-clock.txt | 3 Marvell MVEBU SoCs usually allow to determine core clock frequencies by
|
| H A D | arm,syscon-icst.yaml | 21 these frequencies, the system controller must first be unlocked by
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | sm501.rst | 70 of the M1XCLK and M1CLK frequencies. These two clocks
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-fm-rx.rst | 73 frequencies. Depending on the region, a time constant of either 50
|
| H A D | vidioc-g-dv-timings.rst | 266 the transmitter can't generate such frequencies, then the flag
279 generate such frequencies, then the flag will be cleared.
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,smd-rpm.yaml | 13 frequencies.
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | qcom,rpm-proc.yaml | 37 clocks, regulators and bus frequencies. It implements multiple separate
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | sdm660.dtsi | 22 * framework not supporting multiple frequencies
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/dvb-apps/files/dvb-scan-table/atsc/ |
| H A D | us-NTSC-center-frequencies-8VSB | 1 # US NTSC center frequencies, use if in doubt
|
| H A D | us-ATSC-center-frequencies-8VSB | 1 # US ATSC center frequencies, use if in doubt
|
| /openbmc/linux/drivers/soc/qcom/ |
| H A D | Kconfig | 201 frequencies controlled by the RPM on these devices.
288 memory throughput even with lower CPU frequencies.
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | nvidia,tegra186-mc.yaml | 68 can be used to obtain the set of available frequencies.
|
| /openbmc/linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap3-n950.dts | 82 link-frequencies = /bits/ 64 <210000000 333600000 398400000>;
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | dvb_intro.rst | 99 The frequencies broadcast by Mount Dandenong transmitters are,
123 command line which contains the transponder frequencies. Here is a
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | design.rst | 161 that assumed to have the same access frequencies into a region. As long as the
162 assumption (pages in a region have the same access frequencies) is kept, only
178 fulfill the assumption (pages in same region have similar access frequencies),
183 For each ``aggregation interval``, it compares the access frequencies of
|
| /openbmc/linux/Documentation/devicetree/bindings/opp/ |
| H A D | opp-v2-kryo-cpu.yaml | 17 the CPU frequencies subset and voltage value of each OPP varies based on
|
| /openbmc/linux/Documentation/devicetree/bindings/i3c/ |
| H A D | i3c.yaml | 94 not tolerant to high frequencies
|