Home
last modified time | relevance | path

Searched refs:scaling (Results 1 – 25 of 239) sorted by relevance

12345678910

/OK3568_Linux_fs/buildroot/package/frecon/
H A D0009-Support-FB-rotating-and-scaling-with-environment.patch4 Subject: [PATCH 9/9] Support FB rotating and scaling with environment
36 fb->buffer_properties.scaling = 2;
60 + fb->buffer_properties.scaling = atoi(buf);
61 + if (fb->buffer_properties.scaling < 1)
62 + fb->buffer_properties.scaling = 1;
75 int scaling = font_get_scaling();
76 - if (zoom_in && scaling < 4)
78 scaling++;
79 else if (!zoom_in && scaling > 1)
80 scaling--;
/OK3568_Linux_fs/kernel/Documentation/admin-guide/pm/
H A Dcpufreq.rst44 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 …]
H A Dintel_pstate.rst17 :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 preformance 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 …]
/OK3568_Linux_fs/kernel/drivers/staging/media/hantro/
H A Dhantro_h264.c199 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()
346 ctrls->scaling = in hantro_h264_dec_prepare_run()
348 if (WARN_ON(!ctrls->scaling)) in hantro_h264_dec_prepare_run()
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/qcom/
H A Dpms405.dtsi93 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>;
H A Dpm8150b.dtsi75 qcom,pre-scaling = <1 1>;
81 qcom,pre-scaling = <1 1>;
87 qcom,pre-scaling = <1 1>;
93 qcom,pre-scaling = <1 1>;
H A Dpm8150l.dtsi75 qcom,pre-scaling = <1 1>;
81 qcom,pre-scaling = <1 1>;
87 qcom,pre-scaling = <1 1>;
H A Dpm8150.dtsi83 qcom,pre-scaling = <1 1>;
89 qcom,pre-scaling = <1 1>;
95 qcom,pre-scaling = <1 1>;
/OK3568_Linux_fs/kernel/Documentation/cpu-freq/
H A Dindex.rst4 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
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/input/
H A Dmicrochip,qt1050.txt41 - 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>;
/OK3568_Linux_fs/kernel/drivers/leds/
H A Dleds-pca963x.c61 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()
/OK3568_Linux_fs/kernel/drivers/cpufreq/
H A DKconfig.arm3 # ARM CPU Frequency scaling drivers
48 Armada8K device has the AP806 which supports scaling
78 ("AVS") to handle voltage and frequency scaling. This driver provides
120 tristate "CPU Frequency scaling support for MediaTek SoCs"
210 CPU Frequency scaling support for S3C2410
218 CPU Frequency scaling support for S3C2412 and S3C2413 SoC CPUs.
221 bool "S3C2416 CPU Frequency scaling support"
227 voltage scaling mode in which it is possible to reduce the
233 bool "Allow voltage scaling for S3C2416 arm core"
236 Enable CPU voltage scaling when entering the dvs mode.
[all …]
H A DKconfig.powerpc3 tristate "CBE frequency scaling"
12 bool "CBE frequency scaling using PMI interface"
51 tristate "CPU frequency scaling for IBM POWERNV platform"
H A Dintel_pstate.c147 int scaling; member
820 return sprintf(buf, "%d\n", ratio * cpu->pstate.scaling); in show_base_frequency()
1238 freq *= cpu->pstate.scaling; in update_qos_request()
1700 trace_cpu_frequency(pstate * cpu->pstate.scaling, cpu->cpu); in intel_pstate_set_pstate()
1729 cpu->pstate.scaling = pstate_funcs.get_scaling(); in intel_pstate_get_cpu_pstates()
1735 cpu->pstate.turbo_freq = phy_max * cpu->pstate.scaling; in intel_pstate_get_cpu_pstates()
1739 cpu->pstate.turbo_freq = cpu->pstate.turbo_pstate * cpu->pstate.scaling; in intel_pstate_get_cpu_pstates()
1742 cpu->pstate.max_freq = cpu->pstate.max_pstate * cpu->pstate.scaling; in intel_pstate_get_cpu_pstates()
1985 trace_cpu_frequency(target_pstate * cpu->pstate.scaling, cpu->cpu); in intel_pstate_adjust_pstate()
2227 max_freq = max_state * cpu->pstate.scaling; in intel_pstate_update_perf_limits()
[all …]
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Ddev-subdev.rst101 :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
335 Selections: cropping, scaling and composition
358 The scaling operation changes the size of the image by scaling it to new
359 dimensions. The scaling ratio isn't specified explicitly, but is implied
368 subdev supports scaling but not composing, the top and left values are
[all …]
H A Dcrop.rst20 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 …]
H A Dselection-api-configuration.rst11 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
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-armhf/share/OpenCV/licenses/
H A Dlibjpeg-turbo-README.md144 - **libjpeg: IDCT scaling extensions in decompressor**<br>
145 libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
177 usefulness of DCT scaling as a means of data reduction and SmartScale as a
183 - **libjpeg: DCT scaling in compressor**<br>
185 There is no technical reason why DCT scaling could not be supported when
187 below), only scaling factors of 1/2, 8/15, 4/7, 8/13, 2/3, 8/11, 4/5, and
201 additional DCT scaling factors.
205 This requires the DCT scaling feature, which is not supported.
208 This requires both the DCT scaling and SmartScale features, which are not
303 - When decompressing using scaling factors of 1/2 and 1/4, because libjpeg v8
[all …]
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/OpenCV-android-sdk/sdk/etc/licenses/
H A Dlibjpeg-turbo-README.md144 - **libjpeg: IDCT scaling extensions in decompressor**<br>
145 libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
177 usefulness of DCT scaling as a means of data reduction and SmartScale as a
183 - **libjpeg: DCT scaling in compressor**<br>
185 There is no technical reason why DCT scaling could not be supported when
187 below), only scaling factors of 1/2, 8/15, 4/7, 8/13, 2/3, 8/11, 4/5, and
201 additional DCT scaling factors.
205 This requires the DCT scaling feature, which is not supported.
208 This requires both the DCT scaling and SmartScale features, which are not
303 - When decompressing using scaling factors of 1/2 and 1/4, because libjpeg v8
[all …]
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-aarch64/share/OpenCV/licenses/
H A Dlibjpeg-turbo-README.md144 - **libjpeg: IDCT scaling extensions in decompressor**<br>
145 libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
177 usefulness of DCT scaling as a means of data reduction and SmartScale as a
183 - **libjpeg: DCT scaling in compressor**<br>
185 There is no technical reason why DCT scaling could not be supported when
187 below), only scaling factors of 1/2, 8/15, 4/7, 8/13, 2/3, 8/11, 4/5, and
201 additional DCT scaling factors.
205 This requires the DCT scaling feature, which is not supported.
208 This requires both the DCT scaling and SmartScale features, which are not
303 - When decompressing using scaling factors of 1/2 and 1/4, because libjpeg v8
[all …]
/OK3568_Linux_fs/kernel/drivers/clk/meson/
H A DKconfig58 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.
/OK3568_Linux_fs/kernel/Documentation/hwmon/
H A Dvt1211.rst84 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)::
/OK3568_Linux_fs/kernel/drivers/gpu/drm/arm/
H A Dmalidp_crtc.c259 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()
/OK3568_Linux_fs/yocto/meta-rockchip/recipes-graphics/wayland/weston_11.0.1/
H A D0016-backend-drm-Support-virtual-screen-size.patch252 + bool scaling;
260 - /* The legacy SetCrtc API doesn't allow us to do scaling, and the
277 + scaling = scanout_state->src_w >> 16 != scanout_state->dest_w ||
300 + if (n_conn == 1 || scaling)
314 + if (scaling && !output->scanout_plane->can_scale) {
315 + weston_log("Couldn't do scaling on output %s\n",
/OK3568_Linux_fs/buildroot/package/weston/
H A D0016-backend-drm-Support-virtual-screen-size.patch252 + bool scaling;
260 - /* The legacy SetCrtc API doesn't allow us to do scaling, and the
277 + scaling = scanout_state->src_w >> 16 != scanout_state->dest_w ||
300 + if (n_conn == 1 || scaling)
314 + if (scaling && !output->scanout_plane->can_scale) {
315 + weston_log("Couldn't do scaling on output %s\n",

12345678910