Home
last modified time | relevance | path

Searched +full:higher +full:- +full:than +full:- +full:threshold (Results 1 – 25 of 505) sorted by relevance

12345678910>>...21

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/thermal/
Dimx-thermal.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/imx-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shawn Guo <shawnguo@kernel.org>
11 - Anson Huang <Anson.Huang@nxp.com>
16 - enum:
17 - fsl,imx6q-tempmon
18 - fsl,imx6sx-tempmon
19 - fsl,imx7d-tempmon
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/
Dimx-thermal.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/imx-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shawn Guo <shawnguo@kernel.org>
11 - Anson Huang <Anson.Huang@nxp.com>
16 - fsl,imx6q-tempmon
17 - fsl,imx6sx-tempmon
18 - fsl,imx7d-tempmon
23 will be triggered when temperature is higher than high threshold,
[all …]
/kernel/linux/linux-6.6/Documentation/tools/rtla/
Dcommon_osnoise_options.rst1 **-a**, **--auto** *us*
4 while debugging the system. It is equivalent to use **-s** *us* **-T 1 -t**.
6 **-p**, **--period** *us*
10 **-r**, **--runtime** *us*
14 **-s**, **--stop** *us*
16 Stop the trace if a single sample is higher than the argument in microseconds.
17 If **-T** is set, it will also save the trace to the output.
19 **-S**, **--stop-total** *us*
21 Stop the trace if the total sample is higher than the argument in microseconds.
22 If **-T** is set, it will also save the trace to the output.
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/mm/damon/
Dlru_sort.rst1 .. SPDX-License-Identifier: GPL-2.0
4 DAMON-based LRU-lists Sorting
7 DAMON-based LRU-lists Sorting (DAMON_LRU_SORT) is a static kernel module that
9 (de)prioritization of pages on their LRU-lists for making LRU-lists a more
12 Where Proactive LRU-lists Sorting is Required?
15 As page-granularity access checking overhead could be significant on huge
23 Because DAMON can identify access patterns of best-effort accuracy while
24 inducing only user-specified range of overhead, proactively running
32 rates that higher than a user-specified threshold) and cold pages (pages of
33 memory regions that showing no access for a time that longer than a
[all …]
/kernel/linux/linux-5.10/Documentation/hwmon/
Dltc2947.rst1 Kernel drivers ltc2947-i2c and ltc2947-spi
10 Addresses scanned: -
14 https://www.analog.com/media/en/technical-documentation/data-sheets/LTC2947.pdf
30 active as soon as a temperature reading is higher than a defined threshold. The
37 The following attributes are supported. Limits are read-write, reset_history
38 is write-only and all the other attributes are read-only.
41 in0_input VP-VM voltage (mV).
42 in0_min Undervoltage threshold
43 in0_max Overvoltage threshold
49 in0_label Channel label (VP-VM)
[all …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dltc2947.rst1 Kernel drivers ltc2947-i2c and ltc2947-spi
10 Addresses scanned: -
14 https://www.analog.com/media/en/technical-documentation/data-sheets/LTC2947.pdf
30 active as soon as a temperature reading is higher than a defined threshold. The
37 The following attributes are supported. Limits are read-write, reset_history
38 is write-only and all the other attributes are read-only.
41 in0_input VP-VM voltage (mV).
42 in0_min Undervoltage threshold
43 in0_max Overvoltage threshold
49 in0_label Channel label (VP-VM)
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dmarvell-armada-370-neta.txt4 - compatible: could be one of the following:
5 "marvell,armada-370-neta"
6 "marvell,armada-xp-neta"
7 "marvell,armada-3700-neta"
8 - reg: address and length of the register set for the device.
9 - interrupts: interrupt for the device
10 - phy: See ethernet.txt file in the same directory.
11 - phy-mode: See ethernet.txt file in the same directory
12 - clocks: List of clocks for this device. At least one clock is
14 clock-names property must be used to identify them.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dbattery.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
14 In smart batteries, these are typically stored in non-volatile memory
16 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
27 Batteries must be referenced by chargers and/or fuel-gauges using a phandle.
28 The phandle's property should be named "monitored-battery".
32 const: simple-battery
34 over-voltage-threshold-microvolt:
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/
Dmarvell-armada-370-neta.txt4 - compatible: could be one of the following:
5 "marvell,armada-370-neta"
6 "marvell,armada-xp-neta"
7 "marvell,armada-3700-neta"
8 "marvell,armada-ac5-neta"
9 - reg: address and length of the register set for the device.
10 - interrupts: interrupt for the device
11 - phy: See ethernet.txt file in the same directory.
12 - phy-mode: See ethernet.txt file in the same directory
13 - clocks: List of clocks for this device. At least one clock is
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/supply/
Dbattery.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
14 In smart batteries, these are typically stored in non-volatile memory
16 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
27 Batteries must be referenced by chargers and/or fuel-gauges using a phandle.
28 The phandle's property should be named "monitored-battery".
32 const: simple-battery
34 device-chemistry:
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/
Dfloppy.rst19 Example: If your kernel is called linux-2.6.9, type the following line
22 linux-2.6.9 floppy=thinkpad
25 of linux-2.6.9::
31 linux-2.6.9 floppy=daring floppy=two_fdc
96 and is thus harder to find, whereas non-dma buffers may be
101 threshold to 10 or lower, in order to limit the number of data
104 If you have a FIFO-able FDC, the floppy driver automatically
105 falls back on non DMA mode if no DMA-able memory can be found.
120 floppy=<threshold>,fifo_depth
121 Sets the FIFO threshold. This is mostly relevant in DMA
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/blockdev/
Dfloppy.rst19 Example: If your kernel is called linux-2.6.9, type the following line
22 linux-2.6.9 floppy=thinkpad
25 of linux-2.6.9::
31 linux-2.6.9 floppy=daring floppy=two_fdc
96 and is thus harder to find, whereas non-dma buffers may be
101 threshold to 10 or lower, in order to limit the number of data
104 If you have a FIFO-able FDC, the floppy driver automatically
105 falls back on non DMA mode if no DMA-able memory can be found.
120 floppy=<threshold>,fifo_depth
121 Sets the FIFO threshold. This is mostly relevant in DMA
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/usb/
Dsnps,dwc3.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Felipe Balbi <balbi@kernel.org>
14 be presented as a standalone DT node with an optional vendor-specific
18 - $ref: usb-drd.yaml#
19 - if:
25 - dr_mode
29 $ref: usb-xhci.yaml#
35 - const: snps,dwc3
[all …]
/kernel/linux/linux-5.10/Documentation/networking/
Dipvs-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
4 IPvs-sysctl
10 am_droprate - INTEGER
16 amemthresh - INTEGER
19 It sets the available memory threshold (in pages), which is
25 backup_only - BOOLEAN
26 - 0 - disabled (default)
27 - not 0 - enabled
32 conn_reuse_mode - INTEGER
33 1 - default
[all …]
/kernel/linux/linux-5.10/drivers/cpuidle/governors/
Dmenu.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * menu.c - the menu idle governor
5 * Copyright (C) 2006-2007 Adam Belay <abelay@novell.com>
40 * -----------------------
47 * Since there are other source of wakeups (interrupts for example) than
58 * getting an interrupt very early is much higher than if we expect 50 micro
61 * (as a special twist, we consider every sleep longer than 50 milliseconds
62 * as perfect; there are no power gains for sleeping longer than this)
68 * Repeatable-interval-detector
69 * ----------------------------
[all …]
Dladder.c2 * ladder.c - the residency ladder algorithm
8 * (C) 2006-2007 Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
32 } threshold; member
46 * ladder_do_selection - prepares private data for a state change
55 ldev->states[old_idx].stats.promotion_count = 0; in ladder_do_selection()
56 ldev->states[old_idx].stats.demotion_count = 0; in ladder_do_selection()
57 dev->last_state_idx = new_idx; in ladder_do_selection()
61 * ladder_select_state - selects the next state to enter
71 int last_idx = dev->last_state_idx; in ladder_select_state()
72 int first_idx = drv->states[0].flags & CPUIDLE_FLAG_POLLING ? 1 : 0; in ladder_select_state()
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
Dcpufreq.rst1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
21 the higher the clock frequency and the higher the voltage, the more instructions
22 can be retired by the CPU over a unit of time, but also the higher the clock
23 frequency and the higher the voltage, the more energy is consumed over a unit of
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
[all …]
Dintel_pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
25 than just an operating frequency or an operating performance point (see the
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
66 -----------
69 hardware-managed P-states (HWP) support. If it works in this mode, the
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/pm/
Dcpufreq.rst1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
21 the higher the clock frequency and the higher the voltage, the more instructions
22 can be retired by the CPU over a unit of time, but also the higher the clock
23 frequency and the higher the voltage, the more energy is consumed over a unit of
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
[all …]
Dintel_pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
22 Documentation/admin-guide/pm/cpufreq.rst if you have not done that yet.]
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
25 than just an operating frequency or an operating performance point (see the
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
66 -----------
[all …]
/kernel/linux/linux-6.6/Documentation/networking/
Dipvs-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
4 IPvs-sysctl
10 am_droprate - INTEGER
16 amemthresh - INTEGER
19 It sets the available memory threshold (in pages), which is
25 backup_only - BOOLEAN
26 - 0 - disabled (default)
27 - not 0 - enabled
32 conn_reuse_mode - INTEGER
33 1 - default
[all …]
/kernel/linux/linux-6.6/drivers/cpuidle/governors/
Dmenu.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * menu.c - the menu idle governor
5 * Copyright (C) 2006-2007 Adam Belay <abelay@novell.com>
42 * -----------------------
49 * Since there are other source of wakeups (interrupts for example) than
60 * getting an interrupt very early is much higher than if we expect 50 micro
63 * (as a special twist, we consider every sleep longer than 50 milliseconds
64 * as perfect; there are no power gains for sleeping longer than this)
70 * Repeatable-interval-detector
71 * ----------------------------
[all …]
Dladder.c2 * ladder.c - the residency ladder algorithm
8 * (C) 2006-2007 Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
32 } threshold; member
46 * ladder_do_selection - prepares private data for a state change
55 ldev->states[old_idx].stats.promotion_count = 0; in ladder_do_selection()
56 ldev->states[old_idx].stats.demotion_count = 0; in ladder_do_selection()
57 dev->last_state_idx = new_idx; in ladder_do_selection()
61 * ladder_select_state - selects the next state to enter
71 int last_idx = dev->last_state_idx; in ladder_select_state()
72 int first_idx = drv->states[0].flags & CPUIDLE_FLAG_POLLING ? 1 : 0; in ladder_select_state()
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Ddebugfs-scmi16 on this SCMI instance <n>, the threshold above which any SCMI
17 command, advertised to have an higher-than-threshold execution
58 Description: Max number of concurrently allowed in-flight SCMI messages for
67 Description: Max number of concurrently allowed in-flight SCMI messages for
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/serial/
Dserial.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
11 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
19 where N is the port number (non-negative decimal integer) as printed on the
28 cts-gpios:
34 dcd-gpios:
40 dsr-gpios:
46 dtr-gpios:
[all …]

12345678910>>...21