Searched +full:wakeup +full:- +full:latency (Results 1 – 25 of 33) sorted by relevance
12
| /Documentation/arch/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 …]
|
| /Documentation/devicetree/bindings/cpu/ |
| D | idle-states.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
11 - Anup Patel <anup@brainfault.org>
15 1 - Introduction
18 ARM and RISC-V systems contain HW capable of managing power consumption
19 dynamically, where cores can be put in different low-power states (ranging
22 run-time, can be specified through device tree bindings representing the
[all …]
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /Documentation/tools/rtla/ |
| D | common_timerlat_description.rst | 2 *timerlat* tracer dispatches a kernel thread per-cpu. These threads
4 the wakeup, they collect and generate useful information for the
5 debugging of operating system timer latency.
8 prints the timer latency at the timer *IRQ* handler and the *Thread*
|
| D | rtla-timerlat-top.rst | 2 rtla-timerlat-top
4 -------------------------------------------
5 Measures the operating system timer latency
6 -------------------------------------------
22 seem with the option **-T**.
35 **--aa-only** *us*
38 Print the auto-analysis if the system hits the stop tracing condition. This option
45 In the example below, the timerlat tracer is dispatched in cpus *1-23* in the
46 automatic trace mode, instructing the tracer to stop if a *40 us* latency or
49 # timerlat -a 40 -c 1-23 -q
[all …]
|
| /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 dependent. 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 …]
|
| /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 …]
|
| D | sleep-states.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
40 also be set up as wakeup devices for S2Idle.
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
44 deeper system suspend variants to provide reduced resume latency. It is always
[all …]
|
| D | intel_idle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 Documentation/admin-guide/pm/cpuidle.rst if you have not done that yet.]
28 processor's functional blocks into low-power states. That instruction takes two
38 only way to pass early-configuration-time parameters to it is via the kernel
42 .. _intel-idle-enumeration-of-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
56 subsystem (see :ref:`idle-states-representation` in
57 Documentation/admin-guide/pm/cpuidle.rst),
66 `below <intel-idle-parameters_>`_.]
[all …]
|
| /Documentation/trace/ |
| D | timerlat-tracer.rst | 6 find sources of wakeup latencies of real-time threads. Like cyclictest,
8 computes a *wakeup latency* value as the difference between the *current
13 -----
28 # _-----=> irqs-off
29 # / _----=> need-resched
30 # | / _---=> hardirq/softirq
31 # || / _--=> preempt-depth
34 # TASK-PID CPU# |||| TIMESTAMP ID CONTEXT LATENCY
36 <idle>-0 [000] d.h1 54.029328: #1 context irq timer_latency 932 ns
37 <...>-867 [000] .... 54.029339: #1 context thread timer_latency 11700 ns
[all …]
|
| D | ftrace.rst | 2 ftrace - Function Tracer
13 - Written for: 2.6.28-rc2
14 - Updated for: 3.10
15 - Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt
16 - Converted to rst format - Changbin Du <changbin.du@intel.com>
19 ------------
24 performance issues that take place outside of user-space.
28 There's latency tracing to examine what occurs between interrupts
41 ----------------------
43 See Documentation/trace/ftrace-design.rst for details for arch porters and such.
[all …]
|
| D | histogram.rst | 33 numeric fields - on an event hit, the value(s) will be added to a
35 in place of an explicit value field - this is simply a count of
45 useful for providing more fine-grained summaries of event data.
69 numeric fields are displayed as base-10 integers. This can be
76 .sym-offset display an address as a symbol and offset
83 .graph display a bar-graph of a value
91 - only the 'hex' modifier can be used for values (because values
94 - the 'execname' modifier can only be used on a 'common_pid'. The
100 pid-specific comm fields in the event itself.
119 are in terms of hashtable entries - if a run uses more entries than
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ----------
26 budget lower than the requested one and under-utilize the CPU, thus
27 losing performance. In other words, one OPP under-utilizes the CPU
33 ----------
58 ---------------
67 latencies as the CPUs will have to wakeup from a deep sleep state.
70 performance penalty and a fixed latency. Mitigation can be increased
78 |------- -------
81 <------>
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | dialog,da7219.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - David Rau <David.Rau.opensource@dm.renesas.com>
13 The DA7219 is an ultra low-power audio codec with
14 in-built advanced accessory detection (AAD) for mobile
16 sample rates up to 96 kHz at 24-bit resolution.
28 VDD-supply:
32 VDDMIC-supply:
36 VDDIO-supply:
[all …]
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | power-mgt.txt | 1 IBM Power-Management Bindings
6 node @power-mgt in the device-tree by the firmware.
9 ----------------
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
15 extent of state-loss, whether timebase is stopped on this
18 - exit-latency: The latency involved in transitioning the state of the
21 - target-residency: The minimum time that the CPU needs to reside in
22 this idle state in order to accrue power-savings
26 ----------------
[all …]
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 cores) is idle after an interrupt or equivalent wakeup event, which means that
89 code, and that causes the kernel to run the architecture-specific
91 until the ``->enable()`` governor callback is invoked for that CPU
103 It is expected to reverse any changes made by the ``->enable()``
143 selection made by the ``->select()`` callback (when it was invoked last
148 quality of service (PM QoS) constraints on the processor wakeup latency into
150 PM QoS wakeup latency constraint for a given CPU, a ``CPUIdle`` governor is
152 :c:func:`cpuidle_governor_latency_req()`. Then, the governor's ``->select()``
190 state to start executing the first instruction after a wakeup from it,
[all …]
|
| /Documentation/driver-api/ |
| D | hsi.rst | 5 ---------------
7 High Speed Synchronous Interface (HSI) is a full duplex, low latency protocol,
8 that is optimized for die-level interconnect between an Application Processor
17 signal can be used to wakeup the chips from standby modes. The signals are
23 +------------+ +---------------+
26 | | - - - - - - CAWAKE - - - - - - >| |
27 | T|------------ CADATA ------------>|R |
28 | X|------------ CAFLAG ------------>|X |
29 | |<----------- ACREADY ------------| |
32 | |< - - - - - ACWAKE - - - - - - -| |
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | fsl-imx-uart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/serial/fsl-imx-uart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Fabio Estevam <festevam@gmail.com>
15 - const: fsl,imx1-uart
16 - const: fsl,imx21-uart
17 - items:
18 - enum:
19 - fsl,imx25-uart
[all …]
|
| /Documentation/accounting/ |
| D | psi.rst | 4 PSI - Pressure Stall Information
11 latency spikes, throughput losses, and run the risk of OOM kills.
14 either play it safe and under-utilize their hardware resources, or
23 scarcity aids users in sizing workloads to hardware--or provisioning
38 respective file in /proc/pressure/ -- cpu, memory, and io.
48 The "full" line indicates the share of time in which all non-idle
63 (in us) is tracked and exported as well, to allow detection of latency
75 generate a wakeup event.
116 Notifications to the userspace are rate-limited to one per tracking window.
118 The trigger will de-register when the file descriptor used to define the
[all …]
|
| /Documentation/driver-api/usb/ |
| D | power-management.rst | 1 .. _usb-power-management:
7 :Date: Last-updated: February 2014
11 ---------
13 * What is Remote Wakeup?
17 * Changing the default idle-delay time
31 -------------------------
35 component is ``suspended`` it is in a nonfunctional low-power state; it
37 ``resumed`` (returned to a functional full-power state) when the kernel
66 What is Remote Wakeup?
67 ----------------------
[all …]
|
| /Documentation/trace/postprocess/ |
| D | trace-vmscan-postprocess.pl | 3 # page reclaim. It makes an attempt to extract some high-level information on
6 # Example usage: trace-vmscan-postprocess.pl < /sys/kernel/tracing/trace_pipe
8 # --read-procstat If the trace lacks process info, get it from /proc
9 # --ignore-pid Aggregate processes of the same name together
31 # Per-order events
43 # High-level events extrapolated from tracepoints
83 if ($current_time - 2 > $sigint_received) {
84 print "SIGINT received, report pending. Hit ctrl-c again to exit\n";
105 'ignore-pid' => \$opt_ignorepid,
106 'read-procstat' => \$opt_read_procstat,
[all …]
|
| /Documentation/power/ |
| D | pci.rst | 13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
50 Devices supporting the native PCI PM usually can generate wakeup signals called
53 to put the device that sent it into the full-power state. However, the PCI Bus
63 preparing the device to generate wakeup signals. In that case, however, it
[all …]
|
| /Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 18 User has to opt-in for VM_BIND mode of binding for an address space (VM)
34 ------------------------
42 -------------------------------
52 "dma-buf: Add an API for exporting sync files"
68 be using the i915_vma active reference tracking. It will instead use dma-resv
78 -------------------
79 By default, BOs can be mapped on multiple VMs and can also be dma-buf
82 dma-resv fence list of all shared BOs mapped on the VM.
87 the VM they are private to and can't be dma-buf exported.
88 All private BOs of a VM share the dma-resv object. Hence during each execbuf
[all …]
|
12