Searched +full:wakeup +full:- +full:counter (Results 1 – 19 of 19) sorted by relevance
/Documentation/devicetree/bindings/power/reset/ |
D | atmel,at91sam9260-shdwc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/power/reset/atmel,at91sam9260-shdwc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Claudiu Beznea <claudiu.beznea@microchip.com> 14 and VDDCORE and the wake-up detection on debounced input lines. 19 - atmel,at91sam9260-shdwc 20 - atmel,at91sam9rl-shdwc 21 - atmel,at91sam9x5-shdwc 29 atmel,wakeup-mode: [all …]
|
/Documentation/devicetree/bindings/mfd/ |
D | st,stm32-lptimer.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mfd/st,stm32-lptimer.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: STMicroelectronics STM32 Low-Power Timers 10 The STM32 Low-Power Timer (LPTIM) is a 16-bit timer that provides several 12 - PWM output (with programmable prescaler, configurable polarity) 13 - Trigger source for STM32 ADC/DAC (LPTIM_OUT) 14 - Several counter modes: 15 - quadrature encoder to detect angular position and direction of rotary [all …]
|
/Documentation/devicetree/bindings/timer/ |
D | spreadtrum,sprd-timer.txt | 3 The Spreadtrum SC9860 platform provides 3 general-purpose timers. 4 These timers can support 32bit or 64bit counter, as well as supporting 5 period mode or one-shot mode, and they are can be wakeup source 9 - compatible: should be "sprd,sc9860-timer" for SC9860 platform. 10 - reg: The register address of the timer device. 11 - interrupts: Should contain the interrupt for the timer device. 12 - clocks: The phandle to the source clock (usually a 32.768 KHz fixed clock). 16 compatible = "sprd,sc9860-timer";
|
/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/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 …]
|
D | runtime_pm.rst | 5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc. 18 put their PM-related work items. It is strongly recommended that pm_wq be 20 them to be synchronized with system-wide power transitions (suspend to RAM, 53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks 57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain, 60 2. Device type of the device, if both dev->type and dev->type->pm are present. 62 3. Device class of the device, if both dev->class and dev->class->pm are 65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present. 69 dev->driver->pm directly (if present). 73 and bus type. Moreover, the high-priority one will always take precedence over [all …]
|
/Documentation/RCU/Design/Expedited-Grace-Periods/ |
D | Expedited-Grace-Periods.rst | 13 There are two flavors of RCU (RCU-preempt and RCU-sched), with an earlier 14 third RCU-bh flavor having been implemented in terms of the other two. 38 RCU-preempt Expedited Grace Periods 41 ``CONFIG_PREEMPTION=y`` kernels implement RCU-preempt. 42 The overall flow of the handling of a given CPU by an RCU-preempt 45 .. kernel-figure:: ExpRCUFlow.svg 59 can check to see if the CPU is currently running in an RCU read-side 63 invocation will provide the needed quiescent-state report. 64 This flag-setting avoids the previous forced preemption of all 65 CPUs that might have RCU read-side critical sections. [all …]
|
/Documentation/devicetree/bindings/usb/ |
D | snps,dwc3.yaml | 1 # 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 …]
|
/Documentation/RCU/ |
D | stallwarn.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 options that can be used to fine-tune the detector's operation. Finally, 20 - A CPU looping in an RCU read-side critical section. 22 - A CPU looping with interrupts disabled. 24 - A CPU looping with preemption disabled. 26 - A CPU looping with bottom halves disabled. 28 - For !CONFIG_PREEMPTION kernels, a CPU looping anywhere in the 33 - Booting Linux using a console connection that is too slow to 34 keep up with the boot-time console-message rate. For example, 36 with boot-time message rates, and will frequently result in [all …]
|
/Documentation/admin-guide/thermal/ |
D | intel_powerclamp.rst | 6 - Arjan van de Ven <arjan@linux.intel.com> 7 - Jacob Pan <jacob.jun.pan@linux.intel.com> 12 - Goals and Objectives 15 - Idle Injection 16 - Calibration 19 - Effectiveness and Limitations 20 - Power vs Performance 21 - Scalability 22 - Calibration 23 - Comparison with Alternative Techniques [all …]
|
/Documentation/trace/ |
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. 41 ---------------------- 43 See Documentation/trace/ftrace-design.rst for details for arch porters and such. 47 --------------- [all …]
|
D | histogram-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0 20 generally be truncated - only enough to make the point is displayed. 35 can do with histograms - create one with a single key on a single 63 The hitcount value is a per-bucket value that's automatically 86 (in most cases - some hist_fields such as hitcount don't directly map 87 to an event field in the trace buffer - in these cases the function 89 indicates which type of field it is - key, value, variable, variable 95 lock-free hash table used to implement histograms (see 97 low-level data structures implementing the tracing_map). For the 107 Below that is a diagram of a run-time snapshot of what the tracing_map [all …]
|
/Documentation/RCU/Design/Memory-Ordering/ |
D | Tree-RCU-Memory-Ordering.rst | 2 A Tour Through TREE_RCU's Grace-Period Memory Ordering 13 grace-period memory ordering guarantee is provided. 18 RCU grace periods provide extremely strong memory-ordering guarantees 19 for non-idle non-offline code. 22 period that are within RCU read-side critical sections. 25 of that grace period that are within RCU read-side critical sections. 27 Note well that RCU-sched read-side critical sections include any region 30 an extremely small region of preemption-disabled code, one can think of 37 a linked RCU-protected data structure, and phase two frees that element. 39 phase-one update (in the common case, removal) must not witness state [all …]
|
/Documentation/scheduler/ |
D | sched-util-clamp.rst | 1 .. SPDX-License-Identifier: GPL-2.0 57 foreground, top-app, etc. Util clamp can be used to constrain how much 60 the ones belonging to the currently active app (top-app group). Beside this 65 1. The big cores are free to run top-app tasks immediately. top-app 106 Note that by design RT tasks don't have per-task PELT signal and must always 114 See :ref:`section 3.4 <uclamp-default-values>` for default values and 115 :ref:`3.4.1 <sched-util-clamp-min-rt-default>` on how to change RT tasks 150 task on the rq to only a subset of tasks on the top-most bucket. 152 When a task is enqueued, the counter in the matching bucket is incremented, 157 uclamp value of the rq. See :ref:`section 2.1 <uclamp-buckets>` for details on [all …]
|
/Documentation/admin-guide/sysctl/ |
D | vm.rst | 13 ------------------------------------------------------------------------------ 27 - admin_reserve_kbytes 28 - compact_memory 29 - compaction_proactiveness 30 - compact_unevictable_allowed 31 - dirty_background_bytes 32 - dirty_background_ratio 33 - dirty_bytes 34 - dirty_expire_centisecs 35 - dirty_ratio [all …]
|
/Documentation/virt/kvm/ |
D | api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation 13 - System ioctls: These query and set global attributes which affect the 17 - VM ioctls: These query and set attributes that affect an entire virtual 24 - vcpu ioctls: These query and set attributes that control the operation 32 - device ioctls: These query and set attributes that control the operation 80 facility that allows backward-compatible extensions to the API to be 104 the ioctl returns -ENOTTY. 122 ----------------------- 139 ----------------- [all …]
|
/Documentation/ |
D | memory-barriers.txt | 19 documentation at tools/memory-model/. Nevertheless, even this memory 37 Note also that it is possible that a barrier may be a no-op for an 48 - Device operations. 49 - Guarantees. 53 - Varieties of memory barrier. 54 - What may not be assumed about memory barriers? 55 - Address-dependency barriers (historical). 56 - Control dependencies. 57 - SMP barrier pairing. 58 - Examples of memory barrier sequences. [all …]
|
/Documentation/admin-guide/ |
D | kernel-parameters.txt | 5 force -- enable ACPI if default was off 6 on -- enable ACPI but allow fallback to DT [arm64,riscv64] 7 off -- disable ACPI if default was on 8 noirq -- do not use ACPI for IRQ routing 9 strict -- Be less tolerant of platforms that are not 11 rsdt -- prefer RSDT over (default) XSDT 12 copy_dsdt -- copy DSDT to memory 26 If set to vendor, prefer vendor-specific driver 58 Documentation/firmware-guide/acpi/debug.rst for more information about 116 Format: <byte> or <bitmap-list> [all …]
|
/Documentation/scsi/ |
D | ChangeLog.lpfc | 2 * Please read the associated RELEASE-NOTES file !!! 8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now 19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1. 26 * Added PCI ID for LP10000-S. 31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent 33 - was causing spurious 0710 messages. 55 - stop using volatile. if you need special ordering use memory 57 - switch lpfc_sli_pcimem_bcopy to take void * arguments. 58 - remove typecast for constants - a U postfix marks them 60 - add a MAILBOX_CMD_SIZE macro, as most users of [all …]
|