Home
last modified time | relevance | path

Searched full:states (Results 1 – 25 of 1923) sorted by relevance

12345678910>>...77

/Linux-v5.15/arch/h8300/lib/
Dmulsi3.S9 ; 16b * 16b = 372 states (worst case)
10 ; 32b * 32b = 724 states (worst case)
14 ; 16b * 16b = 48 states
15 ; 16b * 32b = 72 states
16 ; 32b * 32b = 92 states
21 mov.w r1,r2 ; ( 2 states) b * d
22 mulxu r0,er2 ; (22 states)
24 mov.w e0,r3 ; ( 2 states) a * d
25 beq L_skip1 ; ( 4 states)
26 mulxu r1,er3 ; (22 states)
[all …]
/Linux-v5.15/Documentation/admin-guide/pm/
Dintel_idle.rst28 processor's functional blocks into low-power states. That instruction takes two
42 .. _intel-idle-enumeration-of-states:
44 Enumeration of Idle States
50 as C-states (in the ACPI terminology) or idle states. The list of meaningful
51 ``MWAIT`` hint values and idle states (i.e. low-power configurations of the
55 In order to create a list of available idle states required by the ``CPUIdle``
56 subsystem (see :ref:`idle-states-representation` in
58 ``intel_idle`` can use two sources of information: static tables of idle states
69 states, ``intel_idle`` first looks for a ``_CST`` object under one of the ACPI
72 ``CPUIdle`` subsystem expects that the list of idle states supplied by the
[all …]
Dstrategies.rst15 One of them is based on using global low-power states of the whole system in
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
18 kernel puts the system into one of these states when requested by user space
21 user space code can run. Because sleep states are global and the whole system
26 <working-state>`, is based on adjusting the power states of individual hardware
30 a metastate covering a range of different power states of the system in which
32 ``inactive`` (idle). If they are active, they have to be in power states
34 are inactive, ideally, they should be in low-power states in which they may not
43 for the same system in a sleep state. However, transitions from sleep states
47 sleep states than when they are runtime idle most of the time.
Dintel_pstate.rst27 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
69 hardware-managed P-states (HWP) support. If it works in this mode, the
89 depends on whether or not the hardware-managed P-states (HWP) feature has been
106 select P-states by itself, but still it can give hints to the processor's
130 Also, in this configuration the range of P-states available to the processor's
182 registers of the CPU. It generally selects P-states proportional to the
199 hardware-managed P-states (HWP) support. It is always used if the
223 the entire range of available P-states is exposed by ``intel_pstate`` to the
232 Turbo P-states Support
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/arm/
Didle-states.yaml4 $id: http://devicetree.org/schemas/arm/idle-states.yaml#
7 title: ARM idle states binding description
18 where cores can be put in different low-power states (ranging from simple wfi
19 to power gating) according to OS PM policies. The CPU states representing the
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.
25 power states an ARM CPU can be put into are identified by the following list:
33 The power states described in the SBSA document define the basic CPU states on
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
[all …]
/Linux-v5.15/drivers/regulator/
Dgpio-regulator.c39 struct gpio_regulator_state *states; member
51 if (data->states[ptr].gpios == data->state) in gpio_regulator_get_value()
52 return data->states[ptr].value; in gpio_regulator_get_value()
65 if (data->states[ptr].value < best_val && in gpio_regulator_set_voltage()
66 data->states[ptr].value >= min_uV && in gpio_regulator_set_voltage()
67 data->states[ptr].value <= max_uV) { in gpio_regulator_set_voltage()
68 target = data->states[ptr].gpios; in gpio_regulator_set_voltage()
69 best_val = data->states[ptr].value; in gpio_regulator_set_voltage()
94 return data->states[selector].value; in gpio_regulator_list_voltage()
104 if (data->states[ptr].value > best_val && in gpio_regulator_set_current_limit()
[all …]
Dbd71828-regulator.c283 * BUCK3 only supports single voltage for all states.
285 * though => allow setting all states to support
286 * enabling power rail on different states.
324 * BUCK4 only supports single voltage for all states.
326 * though => allow setting all states to support
327 * enabling power rail on different states.
365 * BUCK5 only supports single voltage for all states.
367 * though => allow setting all states to support
368 * enabling power rail on different states.
488 * LDO1 only supports single voltage for all states.
[all …]
/Linux-v5.15/drivers/cpuidle/
Dcpuidle-psci-domain.c34 struct genpd_power_state *state = &pd->states[pd->state_idx]; in psci_pd_power_off()
50 static int psci_pd_parse_state_nodes(struct genpd_power_state *states, in psci_pd_parse_state_nodes() argument
57 ret = psci_dt_parse_state_node(to_of_node(states[i].fwnode), in psci_pd_parse_state_nodes()
68 states[i].data = psci_state_buf; in psci_pd_parse_state_nodes()
76 kfree(states[i].data); in psci_pd_parse_state_nodes()
81 struct genpd_power_state **states, int *state_count) in psci_pd_parse_states() argument
85 /* Parse the domain idle states. */ in psci_pd_parse_states()
86 ret = of_genpd_parse_idle_states(np, states, state_count); in psci_pd_parse_states()
91 ret = psci_pd_parse_state_nodes(*states, *state_count); in psci_pd_parse_states()
93 kfree(*states); in psci_pd_parse_states()
[all …]
Ddt_idle_states.c3 * DT idle states parsing code.
9 #define pr_fmt(fmt) "DT idle-states: " fmt
63 * latencies as defined in idle states bindings in init_state_node()
128 * dt_init_idle_driver() - Parse the DT idle states and initialize the
129 * idle driver states array
143 * If DT idle states are detected and are valid the state count and states
147 * Return: number of valid DT idle states parsed, <0 on failure
163 * We get the idle states for the first logical cpu in the in dt_init_idle_driver()
195 pr_warn("State index reached static CPU idle driver states array size\n"); in dt_init_idle_driver()
199 idle_state = &drv->states[state_idx++]; in dt_init_idle_driver()
[all …]
Dcpuidle-psci.c61 u32 *states = data->psci_states; in __psci_enter_domain_idle_state() local
80 state = states[idx]; in __psci_enter_domain_idle_state()
194 * of a shared state for the domain, assumes the domain states are all in psci_dt_cpu_init_topology()
195 * deeper states. in psci_dt_cpu_init_topology()
197 drv->states[state_count - 1].enter = psci_enter_domain_idle_state; in psci_dt_cpu_init_topology()
198 drv->states[state_count - 1].enter_s2idle = psci_enter_s2idle_domain_idle_state; in psci_dt_cpu_init_topology()
241 /* Idle states parsed correctly, store them in the per-cpu struct. */ in psci_dt_cpu_init_idle()
254 * idle states must not be enabled, so bail out in psci_cpu_init_idle()
310 * PSCI idle states relies on architectural WFI to be represented as in psci_idle_init_cpu()
313 drv->states[0].enter = psci_enter_idle_state; in psci_idle_init_cpu()
[all …]
Dcpuidle-mvebu-v7.c36 if (drv->states[index].flags & MVEBU_V7_FLAG_DEEP_IDLE) in mvebu_v7_enter_idle()
50 .states[0] = ARM_CPUIDLE_WFI_STATE,
51 .states[1] = {
59 .states[2] = {
73 .states[0] = ARM_CPUIDLE_WFI_STATE,
74 .states[1] = {
88 .states[0] = ARM_CPUIDLE_WFI_STATE,
89 .states[1] = {
/Linux-v5.15/tools/power/cpupower/man/
Dcpupower-idle-set.112 sleep states. This can be handy for power vs performance tuning.
23 Disable all idle states with a equal or higher latency than <LATENCY>.
25 Enable all idle states with a latency lower than <LATENCY>.
28 Enable all idle states if not enabled already.
32 Cpuidle Governors Policy on Disabling Sleep States
36 how to choose sleep states, subsequent sleep states on this core, might get
46 then all deeper states are disabled as well. Likewise, if one enables a
53 If criteria are not met to enter deeper sleep states and the lightest sleep
63 By default processor sleep states of all CPU cores are set. Please refer
65 C-states of specific cores.
Dcpupower-idle-info.115 Only print a summary of all available C-states in the system.
28 good overview about the usage and availability of processor sleep states on
31 Be aware that the sleep states as exported by the hardware or BIOS and used by
37 which monitor the duration of sleep states the processor resided in. The
57 The acpi_idle cpuidle driver retrieves available sleep states (C\-states) from
70 ignores ACPI BIOS exported processor sleep states tables.
/Linux-v5.15/Documentation/devicetree/bindings/powerpc/opal/
Dpower-mgt.txt5 idle states. The description of these idle states is exposed via the
14 - flags: indicating some aspects of this idle states such as the
16 idle states and so on. The flag bits are as follows:
27 The following properties provide details about the idle states. These
32 If idle-states are defined, then the properties
38 Array of strings containing the names of the idle states.
42 flags associated with the the aforementioned idle-states. The
62 exit-latencies (in ns) for the idle states in
67 target-residency (in ns) for the idle states in
75 PSSCR for each of the idle states in ibm,cpu-idle-state-names.
[all …]
/Linux-v5.15/Documentation/ABI/testing/
Dsysfs-devices-power15 from sleep states, such as the memory sleep state (suspend to
33 be enabled to wake up the system from sleep states.
87 the system from sleep states, this attribute is not present.
89 states, this attribute is empty.
99 system from sleep states, this attribute is not present. If
101 states, this attribute is empty.
111 is not capable to wake up the system from sleep states, this
113 up the system from sleep states, this attribute is empty.
123 from sleep states, this attribute is not present. If the
124 device is not enabled to wake up the system from sleep states,
[all …]
/Linux-v5.15/drivers/cpuidle/governors/
Dladder.c40 struct ladder_device_state states[CPUIDLE_STATE_MAX]; member
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()
72 int first_idx = drv->states[0].flags & CPUIDLE_FLAG_POLLING ? 1 : 0; in ladder_select_state()
82 last_state = &ldev->states[last_idx]; in ladder_select_state()
84 last_residency = dev->last_residency_ns - drv->states[last_idx].exit_latency_ns; in ladder_select_state()
90 drv->states[last_idx + 1].exit_latency_ns <= latency_req) { in ladder_select_state()
102 drv->states[last_idx].exit_latency_ns > latency_req)) { in ladder_select_state()
106 if (drv->states[i].exit_latency_ns <= latency_req) in ladder_select_state()
136 int first_idx = drv->states[0].flags & CPUIDLE_FLAG_POLLING ? 1 : 0; in ladder_enable_device()
[all …]
Dteo.c15 * wakeups from idle states. Moreover, information about what happened in the
20 * states to choose instead of it.
35 * idle states provided by the %CPUIdle driver in the ascending order. That is,
70 * and all of the deeper idle states (it represents the cases in which the
74 * - The sum of the "intercepts" metrics for all of the idle states shallower
79 * - The sum of the numbers of recent intercepts for all of the idle states
86 * - Traverse the idle states shallower than the candidate one in the
90 * of the numbers of recent intercepts over all of the idle states between
174 u64 lat_ns = drv->states[dev->last_state_idx].exit_latency_ns; in teo_update()
204 s64 target_residency_ns = drv->states[i].target_residency_ns; in teo_update()
[all …]
/Linux-v5.15/sound/usb/misc/
Dua101.c65 /* bits in struct ua101::states */
90 unsigned long states; member
158 if (test_and_clear_bit(USB_CAPTURE_RUNNING, &ua->states)) { in abort_usb_capture()
166 if (test_and_clear_bit(USB_PLAYBACK_RUNNING, &ua->states)) in abort_usb_playback()
185 if (test_bit(USB_PLAYBACK_RUNNING, &ua->states)) { in playback_urb_complete()
205 set_bit(PLAYBACK_URB_COMPLETED, &ua->states); in first_playback_urb_complete()
258 if (unlikely(!test_bit(USB_PLAYBACK_RUNNING, &ua->states))) in playback_work()
288 if (test_bit(ALSA_PLAYBACK_RUNNING, &ua->states)) in playback_work()
369 if (frames > 0 && test_bit(ALSA_CAPTURE_RUNNING, &ua->states)) in capture_urb_complete()
374 if (test_bit(USB_CAPTURE_RUNNING, &ua->states)) { in capture_urb_complete()
[all …]
/Linux-v5.15/drivers/cpufreq/
Dia64-acpi-cpufreq.c28 MODULE_DESCRIPTION("ACPI Processor P-States Driver");
97 if (value == data->acpi_data.states[i].status) in extract_clock()
98 return data->acpi_data.states[i].core_frequency; in extract_clock()
100 return data->acpi_data.states[i-1].core_frequency; in extract_clock()
159 value = (u32) data->acpi_data.states[state].control; in processor_set_freq()
226 pr_debug("No P-States\n"); in acpi_cpufreq_cpu_init()
254 if ((data->acpi_data.states[i].transition_latency * 1000) > in acpi_cpufreq_cpu_init()
257 data->acpi_data.states[i].transition_latency * 1000; in acpi_cpufreq_cpu_init()
266 data->acpi_data.states[i].core_frequency * 1000; in acpi_cpufreq_cpu_init()
282 (u32) data->acpi_data.states[i].core_frequency, in acpi_cpufreq_cpu_init()
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/arm/msm/
Dqcom,idle-state.txt1 QCOM Idle States for cpuidle driver
3 ARM provides idle-state node to define the cpuidle states, as defined in [1].
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
59 the idle-states device node.
75 idle-states {
84 [1]. Documentation/devicetree/bindings/arm/idle-states.yaml
/Linux-v5.15/Documentation/devicetree/bindings/power/
Dpower-domain.yaml30 domain-idle-states:
33 Phandles of idle states that defines the available states for the
37 Note that, the domain-idle-state property reflects the idle states of this
38 PM domain and not the idle states of the devices or sub-domains in the PM
39 domain. Devices and sub-domains have their own idle states independent of
40 the parent domain's idle states. In the absence of this property, the
108 domain-idle-states = <&DOMAIN_RET>, <&DOMAIN_PWR_DN>;
116 domain-idle-states = <&DOMAIN_PWR_DN>;
119 domain-idle-states {
/Linux-v5.15/Documentation/driver-api/pm/
Dcpuidle.rst25 However, there may be multiple different idle states that can be used in such a
35 units: *governors* responsible for selecting idle states to ask the processor
85 struct cpuidle_state objects representing idle states that the
117 The list of idle states to take into consideration is represented by the
118 :c:member:`states` array of struct cpuidle_state objects held by the
149 account when selecting idle states. In order to obtain the current effective
164 First of all, a ``CPUIdle`` driver has to populate the :c:member:`states` array
167 idle states that the processor hardware can be asked to enter shared by all of
170 The entries in the :c:member:`states` array are expected to be sorted by the
214 :c:member:`states` array representing the idle state to ask the processor to
[all …]
/Linux-v5.15/Documentation/admin-guide/blockdev/drbd/
Dfigures.rst20 .. kernel-figure:: conn-states-8.dot
21 :alt: conn-states-8.dot
24 .. kernel-figure:: disk-states-8.dot
25 :alt: disk-states-8.dot
28 .. kernel-figure:: node-states-8.dot
29 :alt: node-states-8.dot
/Linux-v5.15/drivers/acpi/
Dprocessor_idle.c135 * Check, if one of the previous states already marked the lapic in lapic_timer_check_state()
165 return cx - pr->power.states >= pr->power.timer_broadcast_on_state; in lapic_timer_needs_broadcast()
193 * C/P/S0/S1 states when this bit is set. in tsc_check_state()
215 pr->power.states[ACPI_STATE_C2].type = ACPI_STATE_C2; in acpi_processor_get_power_info_fadt()
216 pr->power.states[ACPI_STATE_C3].type = ACPI_STATE_C3; in acpi_processor_get_power_info_fadt()
229 pr->power.states[ACPI_STATE_C2].address = pr->pblk + 4; in acpi_processor_get_power_info_fadt()
230 pr->power.states[ACPI_STATE_C3].address = pr->pblk + 5; in acpi_processor_get_power_info_fadt()
233 pr->power.states[ACPI_STATE_C2].latency = acpi_gbl_FADT.c2_latency; in acpi_processor_get_power_info_fadt()
234 pr->power.states[ACPI_STATE_C3].latency = acpi_gbl_FADT.c3_latency; in acpi_processor_get_power_info_fadt()
244 pr->power.states[ACPI_STATE_C2].address = 0; in acpi_processor_get_power_info_fadt()
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/regulator/
Drohm,bd71815-regulator.yaml55 PMIC "RUN" state voltage in uV when PMIC HW states are used. See
75 PMIC "SUSPEND" state voltage in uV when PMIC HW states are used. See
84 PMIC "LPSR" state voltage in uV when PMIC HW states are used. See
91 # Bucks 1 and 2 support giving separate voltages for operational states
92 # (RUN /CLEAN according to data-sheet) and non operational states
99 # Given RUN voltage is used at all states if regulator is enabled at
101 # Values given for other states are regarded as enable/disable at
105 # for each of the HW states (RUN/SNVS/SUSPEND/LPSR). HW defaults can

12345678910>>...77