| /Linux-v5.4/arch/arm64/boot/dts/qcom/ |
| 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 | 37 qcom,pre-scaling = <1 1>;
43 qcom,pre-scaling = <1 1>;
49 qcom,pre-scaling = <1 1>;
55 qcom,pre-scaling = <1 1>;
|
| D | pm8150l.dtsi | 37 qcom,pre-scaling = <1 1>;
43 qcom,pre-scaling = <1 1>;
49 qcom,pre-scaling = <1 1>;
|
| D | pm8150.dtsi | 45 qcom,pre-scaling = <1 1>;
51 qcom,pre-scaling = <1 1>;
57 qcom,pre-scaling = <1 1>;
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 45 to as CPU performance scaling or CPU frequency scaling (because it involves
52 The Linux kernel supports CPU performance scaling by means of the ``CPUFreq``
53 (CPU Frequency scaling) subsystem that consists of three layers of code: the
54 core, scaling governors and scaling drivers.
57 interfaces for all platforms that support CPU performance scaling. It defines
61 As a rule, each governor implements one, possibly parametrized, scaling
64 Scaling drivers talk to the hardware. They provide scaling governors with
67 by scaling governors.
69 In principle, all available scaling governors can be used with every scaling
71 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
69 In this mode the driver bypasses the scaling governors layer of ``CPUFreq`` and
70 provides its own scaling algorithms for P-state selection. Those algorithms
71 can be applied to ``CPUFreq`` policies in the same way as generic scaling
76 They are not generic scaling governors, but their names are the same as the
173 implemented by the generic ``schedutil`` scaling governor except that the
198 Then, the driver behaves like a regular ``CPUFreq`` scaling driver. That is,
199 it is invoked by generic scaling governors when necessary to talk to the
[all …]
|
| /Linux-v5.4/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.4/drivers/staging/media/hantro/ |
| D | hantro_h264.c | 218 const struct v4l2_ctrl_h264_scaling_matrix *scaling = ctrls->scaling; in reorder_scaling_list() local
219 const size_t num_list_4x4 = ARRAY_SIZE(scaling->scaling_list_4x4); in reorder_scaling_list()
220 const size_t list_len_4x4 = ARRAY_SIZE(scaling->scaling_list_4x4[0]); in reorder_scaling_list()
221 const size_t num_list_8x8 = ARRAY_SIZE(scaling->scaling_list_8x8); in reorder_scaling_list()
222 const size_t list_len_8x8 = ARRAY_SIZE(scaling->scaling_list_8x8[0]); in reorder_scaling_list()
234 src = &scaling->scaling_list_4x4[0][0]; in reorder_scaling_list()
242 src = &scaling->scaling_list_8x8[0][0]; in reorder_scaling_list()
576 ctrls->scaling = in hantro_h264_dec_prepare_run()
578 if (WARN_ON(!ctrls->scaling)) in hantro_h264_dec_prepare_run()
|
| /Linux-v5.4/Documentation/cpu-freq/ |
| D | index.txt | 1 CPU frequency and voltage scaling code in the Linux(TM) kernel
13 Clock scaling allows you to change the clock speed of the CPUs on the
55 Clock and voltage scaling for the SA-1100:
56 * http://www.lartmaker.nl/projects/scaling
|
| D | cpufreq-stats.txt | 2 CPU frequency and voltage scaling statistics in the Linux(TM) kernel
115 CPU Frequency scaling --->
116 [*] CPU Frequency scaling
120 "CPU Frequency scaling" (CONFIG_CPU_FREQ) should be enabled to configure
|
| /Linux-v5.4/drivers/cpufreq/ |
| D | Kconfig.arm | 3 # ARM CPU Frequency scaling drivers
47 Armada8K device has the AP806 which supports scaling
83 ("AVS") to handle voltage and frequency scaling. This driver provides
124 tristate "CPU Frequency scaling support for MediaTek SoCs"
205 CPU Frequency scaling support for S3C2410
213 CPU Frequency scaling support for S3C2412 and S3C2413 SoC CPUs.
216 bool "S3C2416 CPU Frequency scaling support"
222 voltage scaling mode in which it is possible to reduce the
228 bool "Allow voltage scaling for S3C2416 arm core"
231 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"
|
| D | intel_pstate.c | 146 int scaling; member
740 return sprintf(buf, "%d\n", ratio * cpu->pstate.scaling); in show_base_frequency()
1121 freq *= cpu->pstate.scaling; in update_qos_request()
1536 trace_cpu_frequency(pstate * cpu->pstate.scaling, cpu->cpu); in intel_pstate_set_pstate()
1566 cpu->pstate.scaling = pstate_funcs.get_scaling(); in intel_pstate_get_cpu_pstates()
1567 cpu->pstate.max_freq = cpu->pstate.max_pstate * cpu->pstate.scaling; in intel_pstate_get_cpu_pstates()
1573 cpu->pstate.turbo_freq = phy_max * cpu->pstate.scaling; in intel_pstate_get_cpu_pstates()
1575 cpu->pstate.turbo_freq = cpu->pstate.turbo_pstate * cpu->pstate.scaling; in intel_pstate_get_cpu_pstates()
1819 trace_cpu_frequency(target_pstate * cpu->pstate.scaling, cpu->cpu); in intel_pstate_adjust_pstate()
2216 policy->min = cpu->pstate.min_pstate * cpu->pstate.scaling; in __intel_pstate_cpu_init()
[all …]
|
| /Linux-v5.4/drivers/leds/ |
| D | leds-pca963x.c | 60 unsigned int scaling; member
220 unsigned int scaling = pca963x->chip->chipdef->scaling; in pca963x_period_scale() local
222 return scaling ? DIV_ROUND_CLOSEST(val * scaling, 1000) : val; in pca963x_period_scale()
334 &chip->scaling)) in pca963x_get_pdata()
335 chip->scaling = 1000; in pca963x_get_pdata()
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | crop.rst | 27 abilities cropping and scaling. Some video output devices can scale an
55 support scaling or the :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` and
77 The cropping, insertion and scaling process
118 Video hardware can have various cropping, insertion and scaling
119 limitations. It may only scale up or down, support only discrete scaling
120 factors, or have different scaling abilities in horizontal and vertical
121 direction. Also it may not support scaling at all. At the same time the
138 Suppose scaling on a video capture device is restricted to a factor 1:1
153 rectangle of 608 × 456 pixels. The present scaling factors limit
225 /* We could check the actual image size now, the actual scaling factor
[all …]
|
| D | dev-subdev.rst | 103 :ref:`pipeline-scaling`, where image scaling can be performed on both
107 .. _pipeline-scaling:
120 scaling on the sensor is required to achieve higher frame rates.
195 - Sub-devices that scale frames using variable scaling factors should
197 modified. If the 1:1 scaling ratio is supported, this means that
208 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 | 18 Video hardware can have various cropping, composing and scaling
19 limitations. It may only scale up or down, support only discrete scaling
20 factors, or have different scaling abilities in the horizontal and
21 vertical directions. Also it may not support scaling at all. At the same
140 An application can detect if scaling is performed by comparing the width
143 scaling is applied. The application can compute the scaling ratios using
|
| D | selection-api-examples.rst | 67 Example: Querying for scaling factors
89 /* computing scaling factors */
|
| D | selection-api-intro.rst | 19 these abilities cropping, scaling and composing.
35 scaling then the cropping and composing rectangles have the same size.
|
| /Linux-v5.4/drivers/clk/meson/ |
| D | Kconfig | 54 want peripherals and CPU frequency scaling to work.
69 Say Y if you want peripherals and CPU frequency scaling to work.
83 Say Y if you want peripherals and CPU frequency scaling to work.
|
| /Linux-v5.4/drivers/staging/media/sunxi/cedrus/ |
| D | cedrus_h264.c | 234 const struct v4l2_ctrl_h264_scaling_matrix *scaling = in cedrus_write_scaling_lists() local
239 scaling->scaling_list_8x8[0], in cedrus_write_scaling_lists()
240 sizeof(scaling->scaling_list_8x8[0])); in cedrus_write_scaling_lists()
243 scaling->scaling_list_8x8[3], in cedrus_write_scaling_lists()
244 sizeof(scaling->scaling_list_8x8[3])); in cedrus_write_scaling_lists()
247 scaling->scaling_list_4x4, in cedrus_write_scaling_lists()
248 sizeof(scaling->scaling_list_4x4)); in cedrus_write_scaling_lists()
|
| /Linux-v5.4/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.4/drivers/gpu/drm/arm/ |
| D | malidp_crtc.c | 259 u8 scaling = cs->scaled_planes_mask; in malidp_crtc_atomic_check_scaling() local
262 if (!scaling) { in malidp_crtc_atomic_check_scaling()
268 if (scaling & (scaling - 1)) in malidp_crtc_atomic_check_scaling()
275 if (!(mp->layer->id & scaling)) in malidp_crtc_atomic_check_scaling()
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | soc-camera.rst | 122 pixel. Changing sensor window sizes preserves any scaling factors, therefore
126 much as possible by modifying scaling factors. If the sensor window cannot be
129 In soc-camera there are two locations, where scaling and cropping can take
132 It is more efficient to perform scaling and cropping in the camera driver to
135 driver may decide to also use its own scaling and cropping to fulfill the user's
142 .s_fmt() and .try_fmt() have to be implemented too. Sensor window and scaling
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/adc/ |
| D | qcom,spmi-vadc.txt | 74 - qcom,pre-scaling:
77 Definition: Used for scaling the channel input signal before the signal is
79 pre-determined ratio and use it for post scaling. Select one from
165 qcom,pre-scaling = <1 3>;
|
