Home
last modified time | relevance | path

Searched refs:hot (Results 1 – 25 of 281) sorted by relevance

12345678910>>...12

/linux/arch/arm64/boot/dts/qcom/
H A Dpurwa.dtsi215 type = "hot";
353 type = "hot";
371 type = "hot";
389 type = "hot";
527 type = "hot";
545 type = "hot";
563 type = "hot";
581 type = "hot";
599 type = "hot";
725 type = "hot";
[all …]
H A Dhamoa-pmics.dtsi28 type = "hot";
48 type = "hot";
68 type = "hot";
88 type = "hot";
108 type = "hot";
128 type = "hot";
148 type = "hot";
168 type = "hot";
188 type = "hot";
H A Dpm8550vs.dtsi26 type = "hot";
46 type = "hot";
66 type = "hot";
86 type = "hot";
H A Dsm8750-pmics.dtsi23 type = "hot";
43 type = "hot";
63 type = "hot";
83 type = "hot";
H A Dmilos.dtsi2176 aoss0-hot {
2179 type = "hot";
2362 aoss1-hot {
2365 type = "hot";
2382 nsphvx0-hot {
2385 type = "hot";
2402 nsphmx1-hot {
2405 type = "hot";
2422 nsphmx0-hot {
2425 type = "hot";
[all …]
H A Dpm8010.dtsi26 type = "hot";
46 type = "hot";
/linux/arch/arm/boot/dts/qcom/
H A Dqcom-ipq8064.dtsi65 cpu-hot {
68 type = "hot";
85 cpu-hot {
88 type = "hot";
105 cpu-hot {
108 type = "hot";
125 cpu-hot {
128 type = "hot";
145 cpu-hot {
148 type = "hot";
[all …]
/linux/Documentation/admin-guide/mm/damon/
H A Dlru_sort.rst31 DAMON_LRU_SORT finds hot pages (pages of memory regions that showing access
34 user-specified threshold) using DAMON, and prioritizes hot pages while
37 the limit, it prioritizes and deprioritizes more hot and cold pages first,
45 benefits for systems having clear hot/cold access patterns under memory
89 [de]prioritizations of the hot and cold memory resulting in this active to
122 Access frequency threshold for hot memory regions identification in permil.
125 identifies the region as hot, and mark it as accessed on the LRU list, so that
268 respectively. Then it means DAMON_LRU_SORT tried to LRU-sort 42 KiB of hot
284 Number of hot memory regions that tried to be LRU-sorted.
289 Total bytes of hot memory regions that tried to be LRU-sorted.
[all …]
/linux/arch/arm64/include/asm/
H A Dmodule.lds.h17 .text.hot : { *(.text.hot) }
/linux/drivers/video/fbdev/core/
H A Dfbcon_ccw.c287 if (par->cursor_state.hot.x || par->cursor_state.hot.y || in ccw_cursor()
289 par->cursor_state.hot.x = cursor.hot.y = 0; in ccw_cursor()
360 cursor.hot.x = par->cursor_state.hot.x; in ccw_cursor()
361 cursor.hot.y = par->cursor_state.hot.y; in ccw_cursor()
H A Dfbcon_cw.c270 if (par->cursor_state.hot.x || par->cursor_state.hot.y || in cw_cursor()
272 par->cursor_state.hot.x = cursor.hot.y = 0; in cw_cursor()
343 cursor.hot.x = par->cursor_state.hot.x; in cw_cursor()
344 cursor.hot.y = par->cursor_state.hot.y; in cw_cursor()
H A Dfbcon_ud.c318 if (par->cursor_state.hot.x || par->cursor_state.hot.y || in ud_cursor()
320 par->cursor_state.hot.x = cursor.hot.y = 0; in ud_cursor()
383 cursor.hot.x = par->cursor_state.hot.x; in ud_cursor()
384 cursor.hot.y = par->cursor_state.hot.y; in ud_cursor()
H A Dbitblit.c323 if (par->cursor_state.hot.x || par->cursor_state.hot.y || in bit_cursor()
325 par->cursor_state.hot.x = cursor.hot.y = 0; in bit_cursor()
384 cursor.hot.x = par->cursor_state.hot.x; in bit_cursor()
385 cursor.hot.y = par->cursor_state.hot.y; in bit_cursor()
/linux/arch/arm/boot/dts/rockchip/
H A Drk3288-veyron-mickey.dts105 * - 1.2 GHz - 1.0 GHz (almost hot)
106 * - 800 MHz (hot)
108 * - 696 MHz - min (very hot)
139 /* At very hot, don't let GPU go over 300 MHz */
200 /* When hot, GPU goes down to 300 MHz */
206 /* When really hot, don't let GPU go _above_ 300 MHz */
/linux/arch/arm64/boot/dts/marvell/
H A Darmada-ap80x.dtsi344 cpu0_hot: cpu0-hot {
357 map0_hot: map0-hot {
377 cpu1_hot: cpu1-hot {
390 map1_hot: map1-hot {
410 cpu2_hot: cpu2-hot {
423 map2_hot: map2-hot {
443 cpu3_hot: cpu3-hot {
/linux/Documentation/driver-api/cxl/platform/
H A Ddevice-hotplug.rst59 A hot-plug capable CXL memory device, such as one which presents multiple
72 Limiting the size to the capacity preset at boot will limit hot-add support
78 in the :doc:`CEDT<acpi/cedt>`. When this occurs, hot-add is not possible.
81 If a future possible device is not described in the CEDT at boot, hot-add
84 For a platform to support hot-add of a full memory device, it must allocate
/linux/drivers/platform/surface/
H A DKconfig87 devices can be (hot-)removed. Hub devices and drivers are required to
187 Driver for out-of-band hot-plug event signaling on Microsoft Surface
188 devices with hot-pluggable PCIe cards.
191 hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those
193 hot-plug signaling. Thus, without this driver, detaching the base
196 for out-of-band hot-plug notifications, ensuring that the device state
199 Select M or Y here, if you want to (fully) support hot-plugging of
/linux/Documentation/devicetree/bindings/thermal/
H A Dmax77620_thermal.txt48 pmic_die_warn_temp_thresh: hot-die {
50 type = "hot";
/linux/drivers/thermal/intel/
H A Dtherm_throt.c306 bool hot; in throttle_active_work() local
309 get_therm_status(state->level, &hot, &temp); in throttle_active_work()
311 if (!hot && temp > state->baseline_temp) { in throttle_active_work()
410 bool hot; in therm_throt_process() local
413 get_therm_status(state->level, &hot, &temp); in therm_throt_process()
/linux/Documentation/admin-guide/laptops/
H A Dthinkpad-acpi.rst192 some important events and also keyboard hot key presses to the operating
197 The driver enables the HKEY ("hot key") event reporting automatically
204 Some of these events refer to hot key presses, but not all of them.
206 The driver will generate events over the input layer for hot keys and
209 assigned to each hot key.
211 The hot key bit mask allows some control over which hot keys generate
218 modified do anything. Not all hot keys can be individually controlled
241 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
242 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
254 nor does it allow one to manipulate the hot key mask when the firmware
[all …]
/linux/Documentation/mm/damon/
H A Dmonitoring_intervals_tuning_example.rst58 The list shows not seemingly hot regions, and only minimum access pattern
86 In short, the parameters provide poor quality monitoring results for hot
132 DAMON found two distinct 4 KiB regions that pretty hot. The regions are also
200 hot regions detection, but starts looking degrading cold regions detection. ::
239 previous setup. And apparently the distribution seems bit biased to hot
/linux/drivers/soc/fsl/qbman/
H A DKconfig60 bool "QMan 'hot potato' data-stashing self-test"
64 This performs a "hot potato" style test enqueuing/dequeuing a frame
/linux/drivers/video/fbdev/aty/
H A Dmach64_cursor.c96 x = cursor->image.dx - cursor->hot.x - info->var.xoffset; in atyfb_cursor()
104 y = cursor->image.dy - cursor->hot.y - info->var.yoffset; in atyfb_cursor()
/linux/arch/arm64/boot/dts/amlogic/
H A Dmeson-a1-ad402.dts103 soc_hot: soc-hot {
106 type = "hot";
/linux/Documentation/driver-api/dmaengine/
H A Dpxa_dma.rst8 a) Transfers hot queuing
70 c) Transfers hot-chaining
104 - then hot-chaining cannot happen, as the channel must be stopped, the
152 - a driver submitted an aligned tx3 => tx3 is hot-chained

12345678910>>...12