| /Linux-v5.15/arch/arm64/boot/dts/qcom/ |
| D | pm660.dtsi | 86 qcom,pre-scaling = <1 1>;
92 qcom,pre-scaling = <1 1>;
98 qcom,pre-scaling = <1 1>;
103 qcom,pre-scaling = <1 1>;
111 qcom,pre-scaling = <1 1>;
119 qcom,pre-scaling = <1 1>;
127 qcom,pre-scaling = <1 1>;
135 qcom,pre-scaling = <1 1>;
143 qcom,pre-scaling = <1 1>;
152 qcom,pre-scaling = <1 3>;
[all …]
|
| D | pms405.dtsi | 93 qcom,pre-scaling = <1 1>;
98 qcom,pre-scaling = <1 1>;
103 qcom,pre-scaling = <1 3>;
108 qcom,pre-scaling = <1 1>;
115 qcom,pre-scaling = <1 1>;
122 qcom,pre-scaling = <1 1>;
129 qcom,pre-scaling = <1 1>;
|
| D | pm8150b.dtsi | 81 qcom,pre-scaling = <1 1>;
87 qcom,pre-scaling = <1 1>;
93 qcom,pre-scaling = <1 1>;
99 qcom,pre-scaling = <1 1>;
|
| D | pmm8155au_2.dtsi | 74 qcom,pre-scaling = <1 1>;
80 qcom,pre-scaling = <1 1>;
86 qcom,pre-scaling = <1 1>;
|
| D | pm8150l.dtsi | 75 qcom,pre-scaling = <1 1>;
81 qcom,pre-scaling = <1 1>;
87 qcom,pre-scaling = <1 1>;
|
| D | pmm8155au_1.dtsi | 82 qcom,pre-scaling = <1 1>;
88 qcom,pre-scaling = <1 1>;
94 qcom,pre-scaling = <1 1>;
|
| D | pm8150.dtsi | 95 qcom,pre-scaling = <1 1>;
101 qcom,pre-scaling = <1 1>;
107 qcom,pre-scaling = <1 1>;
|
| /Linux-v5.15/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 44 to as CPU performance scaling or CPU frequency scaling (because it involves
51 The Linux kernel supports CPU performance scaling by means of the ``CPUFreq``
52 (CPU Frequency scaling) subsystem that consists of three layers of code: the
53 core, scaling governors and scaling drivers.
56 interfaces for all platforms that support CPU performance scaling. It defines
60 As a rule, each governor implements one, possibly parametrized, scaling
63 Scaling drivers talk to the hardware. They provide scaling governors with
66 by scaling governors.
68 In principle, all available scaling governors can be used with every scaling
70 performance scaling algorithms for P-state selection can be represented in a
[all …]
|
| D | intel_pstate.rst | 17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
18 (``CPUFreq``). It is a scaling driver for the Sandy Bridge and later
50 ``sysfs`` which allows another ``CPUFreq`` scaling driver to be loaded and
58 active mode, it uses its own internal performance scaling governor algorithm or
59 allows the hardware to do performance scaling by itself, while in the passive
61 a certain performance scaling algorithm. Which of them will be in effect
73 In this mode the driver bypasses the scaling governors layer of ``CPUFreq`` and
74 provides its own scaling algorithms for P-state selection. Those algorithms
75 can be applied to ``CPUFreq`` policies in the same way as generic scaling
80 They are not generic scaling governors, but their names are the same as the
[all …]
|
| /Linux-v5.15/drivers/staging/media/hantro/ |
| D | hantro_h264.c | 199 const struct v4l2_ctrl_h264_scaling_matrix *scaling = ctrls->scaling; in assemble_scaling_list() local
201 const size_t num_list_4x4 = ARRAY_SIZE(scaling->scaling_list_4x4); in assemble_scaling_list()
202 const size_t list_len_4x4 = ARRAY_SIZE(scaling->scaling_list_4x4[0]); in assemble_scaling_list()
203 const size_t list_len_8x8 = ARRAY_SIZE(scaling->scaling_list_8x8[0]); in assemble_scaling_list()
213 src = (u32 *)&scaling->scaling_list_4x4[i]; in assemble_scaling_list()
220 src = (u32 *)&scaling->scaling_list_8x8[i]; in assemble_scaling_list()
370 ctrls->scaling = in hantro_h264_dec_prepare_run()
372 if (WARN_ON(!ctrls->scaling)) in hantro_h264_dec_prepare_run()
|
| /Linux-v5.15/Documentation/cpu-freq/ |
| D | index.rst | 4 Linux CPUFreq - CPU frequency and voltage scaling code in the Linux(TM) kernel
9 Clock scaling allows you to change the clock speed of the CPUs on the
38 Clock and voltage scaling for the SA-1100:
39 * http://www.lartmaker.nl/projects/scaling
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | qcom-pmx55.dtsi | 45 qcom,pre-scaling = <1 1>;
51 qcom,pre-scaling = <1 1>;
57 qcom,pre-scaling = <1 1>;
63 qcom,pre-scaling = <1 1>;
|
| /Linux-v5.15/Documentation/devicetree/bindings/input/ |
| D | microchip,qt1050.txt | 41 - microchip,average-scaling:
42 The scaling factor which is used to scale the average-samples.
61 microchip,average-scaling = <16>;
69 microchip,average-scaling = <8>;
76 microchip,average-scaling = <16>;
|
| /Linux-v5.15/drivers/leds/ |
| D | leds-pca963x.c | 61 unsigned int scaling; member
227 unsigned int scaling = led->chip->chipdef->scaling; in pca963x_period_scale() local
229 return scaling ? DIV_ROUND_CLOSEST(val * scaling, 1000) : val; in pca963x_period_scale()
298 &chipdef->scaling)) in pca963x_register_leds()
299 chipdef->scaling = 1000; in pca963x_register_leds()
|
| /Linux-v5.15/drivers/cpufreq/ |
| D | intel_pstate.c | 139 int scaling; member
523 int scaling = cpu->pstate.scaling; in intel_pstate_hybrid_hwp_adjust() local
531 pr_debug("CPU%d: HWP-to-frequency scaling factor: %d\n", cpu->cpu, scaling); in intel_pstate_hybrid_hwp_adjust()
540 if (turbo_freq < cpu->pstate.turbo_pstate * scaling) { in intel_pstate_hybrid_hwp_adjust()
542 scaling = DIV_ROUND_UP(turbo_freq, cpu->pstate.turbo_pstate); in intel_pstate_hybrid_hwp_adjust()
543 cpu->pstate.scaling = scaling; in intel_pstate_hybrid_hwp_adjust()
546 cpu->cpu, scaling); in intel_pstate_hybrid_hwp_adjust()
549 cpu->pstate.max_freq = rounddown(cpu->pstate.max_pstate * scaling, in intel_pstate_hybrid_hwp_adjust()
554 scaling); in intel_pstate_hybrid_hwp_adjust()
561 cpu->pstate.min_pstate = DIV_ROUND_UP(cpu->pstate.min_freq, scaling); in intel_pstate_hybrid_hwp_adjust()
[all …]
|
| D | Kconfig.arm | 3 # ARM CPU Frequency scaling drivers
58 Armada8K device has the AP806 which supports scaling
88 ("AVS") to handle voltage and frequency scaling. This driver provides
130 tristate "CPU Frequency scaling support for MediaTek SoCs"
222 CPU Frequency scaling support for S3C2410
230 CPU Frequency scaling support for S3C2412 and S3C2413 SoC CPUs.
233 bool "S3C2416 CPU Frequency scaling support"
239 voltage scaling mode in which it is possible to reduce the
245 bool "Allow voltage scaling for S3C2416 arm core"
248 Enable CPU voltage scaling when entering the dvs mode.
[all …]
|
| D | Kconfig.powerpc | 3 tristate "CBE frequency scaling"
12 bool "CBE frequency scaling using PMI interface"
51 tristate "CPU frequency scaling for IBM POWERNV platform"
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | crop.rst | 20 abilities cropping and scaling. Some video output devices can scale an
48 support scaling or the :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` and
70 The cropping, insertion and scaling process
111 Video hardware can have various cropping, insertion and scaling
112 limitations. It may only scale up or down, support only discrete scaling
113 factors, or have different scaling abilities in horizontal and vertical
114 direction. Also it may not support scaling at all. At the same time the
131 Suppose scaling on a video capture device is restricted to a factor 1:1
146 rectangle of 608 × 456 pixels. The present scaling factors limit
218 /* We could check the actual image size now, the actual scaling factor
[all …]
|
| D | dev-subdev.rst | 101 :ref:`pipeline-scaling`, where image scaling can be performed on both
105 .. _pipeline-scaling:
118 scaling on the sensor is required to achieve higher frame rates.
193 - Sub-devices that scale frames using variable scaling factors should
195 modified. If the 1:1 scaling ratio is supported, this means that
206 for the pipeline described in :ref:`pipeline-scaling` (table columns
337 Selections: cropping, scaling and composition
360 The scaling operation changes the size of the image by scaling it to new
361 dimensions. The scaling ratio isn't specified explicitly, but is implied
370 subdev supports scaling but not composing, the top and left values are
[all …]
|
| D | selection-api-configuration.rst | 11 Video hardware can have various cropping, composing and scaling
12 limitations. It may only scale up or down, support only discrete scaling
13 factors, or have different scaling abilities in the horizontal and
14 vertical directions. Also it may not support scaling at all. At the same
133 An application can detect if scaling is performed by comparing the width
136 scaling is applied. The application can compute the scaling ratios using
|
| /Linux-v5.15/Documentation/translations/zh_CN/cpu-freq/ |
| D | cpufreq-stats.rst | 122 CPU Frequency scaling --->
123 [*] CPU Frequency scaling
127 "CPU Frequency scaling" (CONFIG_CPU_FREQ) 应该被启用以配置cpufreq-stats。
|
| /Linux-v5.15/Documentation/translations/zh_TW/cpu-freq/ |
| D | cpufreq-stats.rst | 121 CPU Frequency scaling --->
122 [*] CPU Frequency scaling
126 "CPU Frequency scaling" (CONFIG_CPU_FREQ) 應該被啓用以配置cpufreq-stats。
|
| /Linux-v5.15/drivers/clk/meson/ |
| D | Kconfig | 58 want peripherals and CPU frequency scaling to work.
74 Say Y if you want peripherals and CPU frequency scaling to work.
89 Say Y if you want peripherals and CPU frequency scaling to work.
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | vt1211.rst | 84 external scaling resistors. This external scaling needs to be compensated for
89 The board level scaling resistors according to VIA's recommendation are as
109 performs the scaling and returns the properly scaled voltage value.
126 internal thermal diode and the driver does all the scaling for temp2 and
128 temp1 and temp3-temp7, scaling depends on the board implementation and needs
155 scaling resistor (Rs)::
|
| /Linux-v5.15/drivers/gpu/drm/arm/ |
| D | malidp_crtc.c | 261 u8 scaling = cs->scaled_planes_mask; in malidp_crtc_atomic_check_scaling() local
264 if (!scaling) { in malidp_crtc_atomic_check_scaling()
270 if (scaling & (scaling - 1)) in malidp_crtc_atomic_check_scaling()
277 if (!(mp->layer->id & scaling)) in malidp_crtc_atomic_check_scaling()
|
