| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | idle-states.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/idle-states.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
14 1 - Introduction
18 where cores can be put in different low-power states (ranging from simple wfi
20 range of dynamic idle states that a processor can enter at run-time, can be
27 - Running
28 - Idle_standby
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 6 1 - Introduction
10 where cores can be put in different low-power states (ranging from simple
12 the range of dynamic idle states that a processor can enter at run-time, can be
19 - Running
20 - Idle_standby
21 - Idle_retention
22 - Sleep
23 - Off
29 wake-up capabilities, hence it is not considered in this document).
31 Idle state parameters (eg entry latency) are platform specific and need to be
[all …]
|
| /kernel/linux/linux-4.19/Documentation/arm/OMAP/ |
| D | omap_pm | 6 authors use these functions to communicate minimum latency or
13 - support the range of power management parameters present in the TI SRF;
15 - separate the drivers from the underlying PM parameter
17 latency framework or something else;
19 - specify PM parameters in terms of fundamental units, such as
20 latency and throughput, rather than units which are specific to OMAP
23 - allow drivers which are shared with other architectures (e.g.,
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
27 - can be implemented immediately with minimal disruption of other
34 1. Set the maximum MPU wakeup latency:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
13 - support the range of power management parameters present in the TI SRF;
15 - separate the drivers from the underlying PM parameter
17 latency framework or something else;
19 - specify PM parameters in terms of fundamental units, such as
20 latency and throughput, rather than units which are specific to OMAP
23 - allow drivers which are shared with other architectures (e.g.,
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
27 - can be implemented immediately with minimal disruption of other
34 1. Set the maximum MPU wakeup latency::
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-power | 9 What: /sys/devices/.../power/wakeup
13 The /sys/devices/.../power/wakeup attribute allows the user
19 Some devices support "wakeup" events, which are hardware signals
21 have one of the following two values for the sysfs power/wakeup
31 For the devices that are not capable of generating system wakeup
40 space to control the run-time power management of the device.
61 with the main suspend/resume thread) during system-wide power
85 of signaled wakeup events associated with the device. This
86 attribute is read-only. If the device is not capable to wake up
96 number of times the processing of wakeup events associated with
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-power | 9 What: /sys/devices/.../power/wakeup
13 The /sys/devices/.../power/wakeup attribute allows the user
19 Some devices support "wakeup" events, which are hardware signals
21 have one of the following two values for the sysfs power/wakeup
31 For the devices that are not capable of generating system wakeup
40 space to control the run-time power management of the device.
61 with the main suspend/resume thread) during system-wide power
85 of signaled wakeup events associated with the device. This
86 attribute is read-only. If the device is not capable to wake up
96 number of times the processing of wakeup events associated with
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
37 software as individual single-core processors. In other words, a CPU is an
46 Second, if the processor is multi-core, each core in it is able to follow at
61 Finally, each core in a multi-core processor may be able to follow more than one
66 multiple individual single-core "processors", referred to as *hardware threads*
67 (or hyper-threads specifically on Intel hardware), that each can follow one
78 ---------
107 next wakeup event, or there are strict latency constraints preventing any of the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/virtual/kvm/ |
| D | halt-polling.txt | 4 The KVM halt polling system provides a feature within KVM whereby the latency
8 vcpus of a single vcore have ceded, the host kernel polls for wakeup conditions
11 Polling provides a latency advantage in cases where the guest can be run again
13 the order of a few micro-seconds, although performance benefits are workload
14 dependant. In the event that no wakeup source arrives during the polling
17 wakeup periods where the time spent halt polling is minimised and the time
24 The powerpc kvm-hv specific case is implemented in:
36 kvm_vcpu->halt_poll_ns
38 or in the case of powerpc kvm-hv, in the vcore struct:
40 kvmppc_vcore->halt_poll_ns
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | marvell-bt-8xxx.txt | 2 ------
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
21 firmware will use the pin to wakeup host system (u16).
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
25 - interrupt-names: Used only for USB based devices (See below)
26 - interrupts : specifies the interrupt pin number to the cpu. For SDIO, the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | marvell-bt-8xxx.txt | 2 ------
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
21 firmware will use the pin to wakeup host system (u16).
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
25 - interrupt-names: Used only for USB based devices (See below)
26 - interrupts : specifies the interrupt pin number to the cpu. For SDIO, the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/ |
| D | halt-polling.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The KVM halt polling system provides a feature within KVM whereby the latency
11 vcpus of a single vcore have ceded, the host kernel polls for wakeup conditions
14 Polling provides a latency advantage in cases where the guest can be run again
16 the order of a few micro-seconds, although performance benefits are workload
17 dependant. In the event that no wakeup source arrives during the polling
20 wakeup periods where the time spent halt polling is minimised and the time
27 The powerpc kvm-hv specific case is implemented in:
39 kvm_vcpu->halt_poll_ns
41 or in the case of powerpc kvm-hv, in the vcore struct:
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/scripts/perl/bin/ |
| D | wakeup-latency-report | 2 # description: system-wide min/max/avg wakeup latency
3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/wakeup-latency.pl
|
| /kernel/linux/linux-5.10/tools/perf/scripts/perl/bin/ |
| D | wakeup-latency-report | 2 # description: system-wide min/max/avg wakeup latency
3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/perl/wakeup-latency.pl
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 8 - compatible: should be set to "st,lis3lv02d-spi"
9 - reg: the chipselect index
10 - spi-max-frequency: maximal bus speed, should be set to 1000000 unless
12 - interrupts: the interrupt generated by the device
15 - compatible: should be set to "st,lis3lv02d"
16 - reg: i2c slave address
17 - Vdd-supply: The input supply for Vdd
18 - Vdd_IO-supply: The input supply for Vdd_IO
23 - st,click-single-{x,y,z}: if present, tells the device to issue an
26 - st,click-double-{x,y,z}: if present, tells the device to issue an
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 8 - compatible: should be set to "st,lis3lv02d-spi"
9 - reg: the chipselect index
10 - spi-max-frequency: maximal bus speed, should be set to 1000000 unless
12 - interrupts: the interrupt generated by the device
15 - compatible: should be set to "st,lis3lv02d"
16 - reg: i2c slave address
17 - Vdd-supply: The input supply for Vdd
18 - Vdd_IO-supply: The input supply for Vdd_IO
23 - st,click-single-{x,y,z}: if present, tells the device to issue an
26 - st,click-double-{x,y,z}: if present, tells the device to issue an
[all …]
|
| /kernel/linux/linux-5.10/drivers/cpuidle/ |
| D | cpuidle-pseries.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * cpuidle-pseries - idle state cpuidle driver.
78 * were soft-disabled in check_and_cede_processor()
92 * "ibm,get-systems-parameter" RTAS call with the token
98 * table with all the parameters to ibm,get-system-parameters.
99 * CEDE_LATENCY_TOKEN corresponds to the token value for Cede Latency
105 * If the platform supports the cede latency settings information system
109 * a. The first byte is the length “N” of each cede latency setting record minus
112 * b. For each supported cede latency setting a cede latency setting record
115 * -----------------------------
[all …]
|
| D | dt_idle_states.c | 1 // SPDX-License-Identifier: GPL-2.0-only
9 #define pr_fmt(fmt) "DT idle-states: " fmt
33 idle_state->enter = match_id->data; in init_state_node()
39 idle_state->enter_s2idle = match_id->data; in init_state_node()
41 err = of_property_read_u32(state_node, "wakeup-latency-us", in init_state_node()
42 &idle_state->exit_latency); in init_state_node()
46 err = of_property_read_u32(state_node, "entry-latency-us", in init_state_node()
49 pr_debug(" * %pOF missing entry-latency-us property\n", in init_state_node()
51 return -EINVAL; in init_state_node()
54 err = of_property_read_u32(state_node, "exit-latency-us", in init_state_node()
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | omap3-gta04a3.dts | 1 // SPDX-License-Identifier: GPL-2.0-only
6 #include "omap3-gta04.dtsi"
18 interrupt-parent = <&gpio3>;
20 Vdd-supply = <&vaux2>;
21 Vdd_IO-supply = <&vaux2>;
23 st,click-single-x;
24 st,click-single-y;
25 st,click-single-z;
26 st,click-thresh-x = <8>;
27 st,click-thresh-y = <8>;
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | omap3-gta04a3.dts | 9 #include "omap3-gta04.dtsi"
21 interrupt-parent = <&gpio3>;
23 Vdd-supply = <&vaux2>;
24 Vdd_IO-supply = <&vaux2>;
26 st,click-single-x;
27 st,click-single-y;
28 st,click-single-z;
29 st,click-thresh-x = <8>;
30 st,click-thresh-y = <8>;
31 st,click-thresh-z = <10>;
[all …]
|
| /kernel/linux/linux-4.19/drivers/cpuidle/ |
| D | dt_idle_states.c | 12 #define pr_fmt(fmt) "DT idle-states: " fmt
34 return -ENODEV; in init_state_node()
40 idle_state->enter = match_id->data; in init_state_node()
46 idle_state->enter_s2idle = match_id->data; in init_state_node()
48 err = of_property_read_u32(state_node, "wakeup-latency-us", in init_state_node()
49 &idle_state->exit_latency); in init_state_node()
53 err = of_property_read_u32(state_node, "entry-latency-us", in init_state_node()
56 pr_debug(" * %pOF missing entry-latency-us property\n", in init_state_node()
58 return -EINVAL; in init_state_node()
61 err = of_property_read_u32(state_node, "exit-latency-us", in init_state_node()
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/bench/ |
| D | futex-wake-parallel.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Block a bunch of threads and let parallel waker threads wakeup an
6 * equal amount of them. The program output reflects the avg latency
27 #include <subcmd/parse-options.h>
47 /* all threads will block on the same futex -- hash bucket chaos ;) */
69 "perf bench futex wake-parallel <options>",
82 waker->nwoken = futex_wake(&futex, nwakes, futex_flag); in waking_workerfn()
83 if (waker->nwoken != nwakes) in waking_workerfn()
84 warnx("couldn't wakeup all tasks (%d/%d)", in waking_workerfn()
85 waker->nwoken, nwakes); in waking_workerfn()
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/bench/ |
| D | futex-wake-parallel.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Block a bunch of threads and let parallel waker threads wakeup an
6 * equal amount of them. The program output reflects the avg latency
27 #include <subcmd/parse-options.h>
46 /* all threads will block on the same futex -- hash bucket chaos ;) */
68 "perf bench futex wake-parallel <options>",
81 waker->nwoken = futex_wake(&futex, nwakes, futex_flag); in waking_workerfn()
82 if (waker->nwoken != nwakes) in waking_workerfn()
83 warnx("couldn't wakeup all tasks (%d/%d)", in waking_workerfn()
84 waker->nwoken, nwakes); in waking_workerfn()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 9 Sleep states are global low-power states of the entire system in which user
24 Suspend-to-Idle
25 ---------------
27 This is a generic, pure software, light-weight variant of system suspend (also
30 I/O devices into low-power states (possibly lower-power than available in the
34 The system is woken up from this state by in-band interrupts, so theoretically
36 also be set up as wakeup devices for S2Idle.
39 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
40 deeper system suspend variants to provide reduced resume latency. It is always
46 -------
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-sched.txt | 1 perf-sched(1)
5 ----
6 perf-sched - Tool to trace/measure scheduler properties (latencies)
9 --------
11 'perf sched' {record|latency|map|replay|script|timehist}
14 -----------
20 'perf sched latency' to report the per task scheduling latencies
30 of the workload as it occurred when it was recorded - and can repeat
33 'perf sched map' to print a textual context-switching outline of
35 individual CPUs, and the two-letter shortcuts stand for tasks that
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/Documentation/ |
| D | perf-sched.txt | 1 perf-sched(1)
5 ----
6 perf-sched - Tool to trace/measure scheduler properties (latencies)
9 --------
11 'perf sched' {record|latency|map|replay|script|timehist}
14 -----------
20 'perf sched latency' to report the per task scheduling latencies
30 of the workload as it occurred when it was recorded - and can repeat
33 'perf sched map' to print a textual context-switching outline of
35 individual CPUs, and the two-letter shortcuts stand for tasks that
[all …]
|