| /freebsd/sys/contrib/device-tree/Bindings/powerpc/opal/ |
| H A D | power-mgt.txt | 5 idle states. The description of these idle states is exposed via the
10 Typically each idle state has the following associated properties:
12 - name: The name of the idle state as defined by the firmware.
14 - flags: indicating some aspects of this idle states such as the
16 idle states and so on. The flag bits are as follows:
19 CPU from idle to running.
22 this idle state in order to accrue power-savings
27 The following properties provide details about the idle states. These
29 provides the value of that property for the idle state associated with
32 If idle-states are defined, then the properties
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/memory-controllers/ |
| H A D | rockchip,rk3399-dmc.yaml | 60 Configure the PD_IDLE value. Defines the power-down idle period in which
61 memories are placed into power-down mode if bus is idle for PD_IDLE DFI
63 See also rockchip,pd-idle-ns.
69 Configure the SR_IDLE value. Defines the self-refresh idle period in
70 which memories are placed into self-refresh mode if bus is idle for
72 See also rockchip,sr-idle-ns.
79 Defines the memory self-refresh and controller clock gating idle period.
81 arg gating started if bus is idle for sr_mc_gate_idle*1024 DFI clock
83 See also rockchip,sr-mc-gate-idle-ns.
89 Defines the self-refresh power down idle perio
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/arm/ |
| H A D | idle-states.yaml | 4 $id: http://devicetree.org/schemas/arm/idle-states.yaml#
7 title: ARM idle states binding description
20 range of dynamic idle states that a processor can enter at run-time, can be
22 enter/exit specific idle states on a given processor.
35 PM implementation to put the processor in different idle states (which include
36 states listed above; "off" state is not an idle state since it does not have
39 Idle state parameters (e.g. entry latency) are platform specific and need to
43 The device tree binding definition for ARM idle states is the subject of this
47 2 - idle-states definitions
50 Idle states are characterized for a specific system through a set of
[all …]
|
| H A D | psci.yaml | 95 idle state nodes with entry-method property is set to "psci", as per
98 [1] Kernel documentation - ARM idle states bindings
99 Documentation/devicetree/bindings/cpu/idle-states.yaml
113 For these cases, the definitions of the idle states for the CPUs and the
114 CPU topology, must conform to the binding in [3]. The idle states
124 [4] Documentation/devicetree/bindings/power/domain-idle-state.yaml
188 // Case 4: CPUs and CPU idle states described using the hierarchical model.
212 idle-states {
215 compatible = "arm,idle-state";
223 domain-idle
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/cpu/ |
| H A D | idle-states.yaml | 4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml#
7 title: Idle states
21 representing the range of dynamic idle states that a processor can enter at
23 parameters required to enter/exit specific idle states on a given processor.
26 2 - ARM idle states
40 PM implementation to put the processor in different idle states (which include
41 states listed above; "off" state is not an idle state since it does not have
44 Idle state parameters (e.g. entry latency) are platform specific and need to
48 The device tree binding definition for ARM idle states is the subject of this
52 3 - RISC-V idle states
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/msm/ |
| H A D | qcom,idle-state.txt | 1 QCOM Idle States for cpuidle driver
3 ARM provides idle-state node to define the cpuidle states, as defined in [1].
4 cpuidle-qcom is the cpuidle driver for Qualcomm SoCs and uses these idle
5 states. Idle states have different enter/exit latency and residency values.
6 The idle states supported by the QCOM SoC are defined as -
18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings
34 between the time it enters idle and the next known wake up. SPC mode is used
37 sequence for this idle state is programmed to power down the supply to the
58 The idle-state for QCOM SoCs are distinguished by the compatible property of
59 the idle-states device node.
[all …]
|
| /freebsd/usr.bin/w/ |
| H A D | pr_time.c | 102 * Display the idle time.
103 * Returns number of excess characters that were used for long idle time.
106 pr_idle(time_t idle) in pr_idle() argument
110 xo_attr("seconds", "%lu", (unsigned long) idle); in pr_idle()
112 xo_emit("{e:idle-seconds/%lu}", (unsigned long) idle); in pr_idle()
114 /* If idle more than 36 hours, print as a number of days. */ in pr_idle()
115 if (idle >= 36 * 3600) { in pr_idle()
116 int days = idle / 86400; in pr_idle()
117 xo_emit(" {q:idle/%dday%s} ", days, days > 1 ? "s" : " " ); in pr_idle()
124 /* If idle more than an hour, print as HH:MM. */ in pr_idle()
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mux/ |
| H A D | mux-controller.yaml | 33 have when it is idle. The idle-state property is used for this. If the
34 idle-state is not present, the mux controller is typically left as is when
35 it is idle. For multiplexer chips that expose several mux controllers, the
36 idle-state property is an array with one idle state for each mux controller.
39 as is when it is idle. This is the default, but can still be useful for
41 there is a need to "step past" a mux controller and set some other idle
45 multiplexer. Using this disconnected high-impedance state as the idle state
46 is indicated with idle state (-2).
62 idle-state = <MUX_IDLE_DISCONNECT MUX_IDLE_AS_IS 2>;
85 idle-state:
[all …]
|
| H A D | mux-controller.txt | 127 have when it is idle. The idle-state property is used for this. If the
128 idle-state is not present, the mux controller is typically left as is when
129 it is idle. For multiplexer chips that expose several mux controllers, the
130 idle-state property is an array with one idle state for each mux controller.
133 as is when it is idle. This is the default, but can still be useful for
135 there is a need to "step past" a mux controller and set some other idle
139 multiplexer. Using this disconnected high-impedance state as the idle state
140 is indicated with idle state (-2).
156 idle-state = <MUX_IDLE_DISCONNECT MUX_IDLE_AS_IS 2>;
|
| /freebsd/sys/contrib/device-tree/Bindings/power/ |
| H A D | domain-idle-state.yaml | 4 $id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
7 title: PM Domain Idle States
13 A domain idle state node represents the state parameters that will be used to
18 const: domain-idle-states
25 Each state node represents a domain idle state description.
29 const: domain-idle-state
33 The worst case latency in microseconds required to enter the idle
39 The worst case latency in microseconds required to exit the idle
44 The minimum residency duration in microseconds after which the idle
46 entering the idle state.
[all …]
|
| H A D | power-domain.yaml | 31 domain-idle-states:
36 Phandles of idle states that defines the available states for the
37 power-domain provider. The idle state definitions are compatible with the
38 domain-idle-state bindings, specified in ./domain-idle-state.yaml.
40 Note that, the domain-idle-state property reflects the idle states of this
41 PM domain and not the idle states of the devices or sub-domains in the PM
42 domain. Devices and sub-domains have their own idle states independent of
43 the parent domain's idle state
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/thermal/ |
| H A D | thermal-idle.yaml | 5 $id: http://devicetree.org/schemas/thermal/thermal-idle.yaml#
8 title: Thermal idle cooling device
14 The thermal idle cooling device allows the system to passively
15 mitigate the temperature on the device by injecting idle cycles,
18 This binding describes the thermal idle node.
22 const: thermal-idle
24 A thermal-idle node describes the idle cooling device properties to
36 The idle duration in microsecond the device should cool down.
40 The exit latency constraint in microsecond for the injected idle state
42 idle state from among all the present ones.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/i2c/ |
| H A D | i2c-mux-pinctrl.txt | 39 The only exception is that no bus will be created for a state named "idle". If
43 pinctrl-names = "ddc", "pta", "idle" -> ddc = bus 0, pta = bus 1
44 pinctrl-names = "ddc", "idle", "pta" -> Invalid ("idle" not last)
45 pinctrl-names = "idle", "ddc", "pta" -> Invalid ("idle" not last)
50 If an idle state is defined, whenever an access is not being made to a device
51 on a child bus, the idle pinctrl state will be programmed into hardware.
53 If an idle state is not defined, the most recently used pinctrl state will be
66 pinctrl-names = "ddc", "pta", "idle";
|
| H A D | i2c-mux-pinctrl.yaml | 34 The only exception is that no bus will be created for a state named "idle". If such a state is
37 pinctrl-names = "ddc", "pta", "idle" -> ddc = bus 0, pta = bus 1
38 pinctrl-names = "ddc", "idle", "pta" -> Invalid ("idle" not last)
39 pinctrl-names = "idle", "ddc", "pta" -> Invalid ("idle" not last)
44 If an idle state is defined, whenever an access is not being made to a device on a child bus,
45 the idle pinctrl state will be programmed into hardware.
47 If an idle state is not defined, the most recently used pinctrl state will be left programmed
77 pinctrl-names = "ddc", "pta", "idle";
|
| H A D | i2c-mux-reg.txt | 23 - idle-state: value to set the muxer to when idle. When no value is
29 If an idle state is defined, using the idle-state (optional) property,
31 register will be set according to the idle value.
33 If an idle state is not defined, the most recently used value will be
|
| /freebsd/lib/libsys/ |
| H A D | rtprio.2 | 60 .Nd examine or modify realtime or idle priority
74 is used to lookup or change the realtime or idle priority of a process,
79 is used to lookup or change the realtime or idle priority of a thread.
128 RTP_PRIO_NORMAL for normal priorities, and RTP_PRIO_IDLE for idle priorities.
136 Realtime and idle priority is inherited through
142 higher priority, or by an interrupt; idle priority threads will run only
144 Higher real/idle priority threads
145 preempt lower real/idle priority threads.
146 Threads of equal real/idle priority are run round-robin.
170 root is allowed to change the realtime or idle priority of any thread.
[all …]
|
| /freebsd/sys/contrib/device-tree/src/arm64/freescale/ |
| H A D | fsl-ls2088a.dtsi | 28 cpu-idle-states = <&CPU_PW20>;
38 cpu-idle-states = <&CPU_PW20>;
48 cpu-idle-states = <&CPU_PW20>;
58 cpu-idle-states = <&CPU_PW20>;
69 cpu-idle-states = <&CPU_PW20>;
78 cpu-idle-states = <&CPU_PW20>;
88 cpu-idle-states = <&CPU_PW20>;
98 cpu-idle-states = <&CPU_PW20>;
128 compatible = "arm,idle-state";
129 idle-state-name = "PW20";
|
| H A D | fsl-ls2080a.dtsi | 28 cpu-idle-states = <&CPU_PW20>;
38 cpu-idle-states = <&CPU_PW20>;
48 cpu-idle-states = <&CPU_PW20>;
58 cpu-idle-states = <&CPU_PW20>;
68 cpu-idle-states = <&CPU_PW20>;
78 cpu-idle-states = <&CPU_PW20>;
89 cpu-idle-states = <&CPU_PW20>;
98 cpu-idle-states = <&CPU_PW20>;
128 compatible = "arm,idle-state";
129 idle-state-name = "PW20";
|
| /freebsd/sys/contrib/device-tree/src/arm64/sprd/ |
| H A D | ums9620.dtsi | 53 cpu-idle-states = <&LIT_CORE_PD>;
61 cpu-idle-states = <&LIT_CORE_PD>;
69 cpu-idle-states = <&LIT_CORE_PD>;
77 cpu-idle-states = <&LIT_CORE_PD>;
85 cpu-idle-states = <&BIG_CORE_PD>;
93 cpu-idle-states = <&BIG_CORE_PD>;
101 cpu-idle-states = <&BIG_CORE_PD>;
109 cpu-idle-states = <&BIG_CORE_PD>;
113 idle-states {
116 compatible = "arm,idle-state";
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | twl4030-power.txt | 11 "ti,twl4030-power-idle"
12 "ti,twl4030-power-idle-osc-off"
17 When using ti,twl4030-power-idle, the TI recommended configuration
18 for idle modes is loaded to the tlw4030 PMIC.
20 When using ti,twl4030-power-idle-osc-off, the TI recommended
22 down during off-idle. Note that this does not work on all boards
|
| /freebsd/share/man/man9/ |
| H A D | runqueue.9 | 56 for idle priority processes.
74 returns zero if there are no runnable processes other than the idle process.
75 If there is at least one runnable process other than the idle process, it
85 In that case the second CPU will simply travel through the idle loop one
87 This works because idle CPUs are not halted in SMP systems.
88 If idle CPUs are halted in SMP systems, then this race condition might have
97 If there are no runnable threads, then the idle thread is returned.
|
| /freebsd/sys/kern/ |
| H A D | kern_idle.c | 46 * Set up per-cpu idle process contexts. The AP's shouldn't be running or
47 * accessing their idle processes at this point, so don't bother with
60 p = NULL; /* start with no idle process */ in idle_setup()
66 RFSTOPPED | RFHIGHPID, 0, "idle", "idle: cpu%d", pc->pc_cpuid); in idle_setup()
70 RFSTOPPED | RFHIGHPID, 0, "idle", "idle"); in idle_setup()
|
| /freebsd/sys/contrib/device-tree/Bindings/devfreq/ |
| H A D | rk3399_dmc.txt | 35 power-down idle period in which memories are
36 placed into power-down mode if bus is idle
40 self-refresh idle period in which memories are
41 placed into self-refresh mode if bus is idle
47 clock gating idle period. Memories are placed
49 clock arg gating started if bus is idle for
52 - rockchip,srpd_lite_idle : Defines the self-refresh power down idle
54 self-refresh power down mode if bus is idle
58 - rockchip,standby_idle : Defines the standby idle period in which
61 be gated if bus is idle for standby_idle * DFI
|
| /freebsd/sys/contrib/device-tree/Bindings/watchdog/ |
| H A D | atmel-sama5d4-wdt.txt | 15 - atmel,idle-halt: present if you want to stop the watchdog when the CPU is
16 in idle state.
18 watchdog not counting when the CPU is in idle state, therefore the
20 if the CPU stop working while it is in idle state, which is probably
33 atmel,idle-halt;
|
| /freebsd/libexec/rpc.rusersd/ |
| H A D | rusers_proc.c | 84 syslog(LOG_ERR, "%s: unable to get idle time", display); in XqueryIdle()
110 u_long idle; in getidle() local
117 if (display && *display && (idle = XqueryIdle(display)) >= 0) in getidle()
118 return(idle); in getidle()
120 idle = 0; in getidle()
129 idle = (kbd_idle < mouse_idle)?kbd_idle:mouse_idle; in getidle()
143 idle = now - st.st_atime; in getidle()
144 idle = (idle + 30) / 60; /* secs->mins */ in getidle()
147 return(idle); in getidle()
|