Searched +full:wakeup +full:- +full:active +full:- +full:high (Results 1 – 25 of 25) sorted by relevance
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | nokia,h4p-bluetooth.txt | 2 --------------------- 8 UART status lines for wakeup of UART transceivers to improve power management 13 - compatible: should contain "nokia,h4p-bluetooth" as well as one of the following: 14 * "brcm,bcm2048-nokia" 15 * "ti,wl1271-bluetooth-nokia" 16 - reset-gpios: GPIO specifier, used to reset the BT module (active low) 17 - bluetooth-wakeup-gpios: GPIO specifier, used to wakeup the BT module (active high) 18 - host-wakeup-gpios: GPIO specifier, used to wakeup the host processor (active high) 19 - clock-names: should be "sysclk" 20 - clocks: should contain a clock specifier for every name in clock-names [all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | atmel,sama5d2-shdwc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/power/reset/atmel,sama5d2-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 - items: 20 - const: microchip,sama7g5-shdwc 21 - const: syscon 22 - enum: [all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-omap.txt | 4 - compatible: 5 - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family. 6 - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family. 7 This RTC IP has special WAKE-EN Register to enable 8 Wakeup generation for event Alarm. It can also be 11 - "ti,am4372-rtc" - for RTC IP used similar to that on AM437X SoC family. 12 - reg: Address range of rtc register set 13 - interrupts: rtc timer, alarm interrupts in order 16 - system-power-controller: whether the rtc is controlling the system power 18 - clocks: Any internal or external clocks feeding in to rtc [all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | brcm,brcmstb-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/gpio/brcm,brcmstb-gpio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 The controller's registers are organized as sets of eight 32-bit 15 - Doug Berger <opendmb@gmail.com> 16 - Florian Fainelli <f.fainelli@gmail.com> 21 - enum: 22 - brcm,bcm7445-gpio 23 - const: brcm,brcmstb-gpio [all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtmv20-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/regulator/richtek,rtmv20-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - ChiYuan Huang <cy_huang@richtek.com> 27 wakeup-source: true 32 enable-gpios: 36 richtek,ld-pulse-delay-us: 38 load current pulse delay in microsecond after strobe pin pulse high. 43 richtek,ld-pulse-width-us: [all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | interrupts.txt | 5 ------------------------- 8 "interrupts" property, an "interrupts-extended" property, or both. If both are 16 interrupt-parent = <&intc1>; 19 The "interrupt-parent" property is used to specify the controller to which 25 The "interrupts-extended" property is a special form; useful when a node needs 31 interrupts-extended = <&intc1 5 1>, <&intc2 1 0>; 34 ----------------------------- 36 A device is marked as an interrupt controller with the "interrupt-controller" 37 property. This is a empty, boolean property. An additional "#interrupt-cells" 45 ----------- [all …]
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 17 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled 25 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every 26 non-dedicated pin can be configured as a GPIO; and most chips have at least 31 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS 36 - Output values are writable (high=1, low=0). Some chips also have 38 value might be driven, supporting "wire-OR" and similar schemes for the 41 - Input values are likewise readable (1, 0). Some chips support readback 42 of pins configured as "output", which is very useful in such "wire-OR" 44 input de-glitch/debounce logic, sometimes with software controls. 46 - Inputs can often be used as IRQ signals, often edge triggered but [all …]
|
| D | consumer.rst | 21 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that 25 - Truly optional GPIOLIB support - where the driver does not really make use 26 of the GPIOs on certain compile-time configurations for certain systems, but 27 will use it under other compile-time configurations. In this case the 35 All the functions that work with the descriptor-based GPIO interface are 45 With the descriptor-based interface, GPIOs are identified with an opaque, 46 non-forgeable handler that must be obtained through a call to one of the 62 see Documentation/driver-api/gpio/board.rst 78 whether the line is configured active high or active low (see 87 with IS_ERR() (they will never return a NULL pointer). -ENOENT will be returned [all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | 8250_omap.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Vignesh Raghavendra <vigneshr@ti.com> 13 - $ref: /schemas/serial/serial.yaml# 14 - $ref: /schemas/serial/rs485.yaml# 19 - enum: 20 - ti,am3352-uart 21 - ti,am4372-uart 22 - ti,am654-uart [all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | wkup-m3-ipc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/soc/ti/wkup-m3-ipc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Wakeup M3 IPC device 10 - Dave Gerlach <d-gerlach@ti.com> 11 - Drew Fustini <dfustini@baylibre.com> 14 The TI AM33xx and AM43xx family of devices use a small Cortex M3 co-processor 15 (commonly referred to as Wakeup M3 or CM3) to help with various low power tasks 17 C-states for CPU Idle. Once the wkup_m3_ipc driver uses the wkup_m3_rproc driver [all …]
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | microchip,ksz.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Marek Vasut <marex@denx.de> 11 - Woojung Huh <Woojung.Huh@microchip.com> 14 - $ref: /schemas/spi/spi-peripheral-props.yaml# 21 - microchip,ksz8765 22 - microchip,ksz8794 23 - microchip,ksz8795 24 - microchip,ksz8863 [all …]
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 9 ---------------- 13 different performance characteristics - on such platforms, not all CPUs can be 23 - not all CPUs may have the same microarchitecture (µarch). 24 - with Dynamic Voltage and Frequency Scaling (DVFS), not all CPUs may be 28 performance-oriented than the LITTLE ones (more pipeline stages, bigger caches, 39 ------------------- 49 while ``original capacity`` is class-agnostic. The rest of this document will use 54 --------------------- 59 Consider an hypothetical dual-core asymmetric CPU capacity system where 61 - work_per_hz(CPU0) = W [all …]
|
| 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. 157 uclamp value of the rq. See :ref:`section 2.1 <uclamp-buckets>` for details on 182 .. _uclamp-buckets: [all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/i2c/i2c-arb-gpio-challenge.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: GPIO-based I2C Arbitration Using a Challenge & Response Mechanism 10 - Doug Anderson <dianders@chromium.org> 11 - Peter Rosin <peda@axentia.se> 18 standard I2C multi-master rules. Using GPIOs is generally useful in the case 30 others can see. These are all active low with pull-ups enabled. We'll 51 const: i2c-arb-gpio-challenge [all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/mmc/mmc-controller.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Ulf Hansson <ulf.hansson@linaro.org> 25 "#address-cells": 30 "#size-cells": 37 broken-cd: 42 cd-gpios: 47 non-removable: [all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | syna,rmi4.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jason A. Donenfeld <Jason@zx2c4.com> 11 - Matthias Schiffer <matthias.schiffer@ew.tq-group.com 12 - Vincent Huang <vincent.huang@tw.synaptics.com> 22 - syna,rmi4-i2c 23 - syna,rmi4-spi 28 '#address-cells': 31 '#size-cells': [all …]
|
| /Documentation/timers/ |
| D | highres.rst | 2 High resolution timers and dynamic ticks design notes 8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf 11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf 23 - hrtimer base infrastructure 24 - timeofday and clock source management 25 - clock event management 26 - high resolution timer functionality 27 - dynamic ticks 31 --------------------------- 40 - time ordered enqueueing into a rb-tree [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/accounting/ |
| D | psi.rst | 4 PSI - Pressure Stall Information 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 75 generate a wakeup event. 104 prevent overly frequent polling. Max limit is chosen as a high enough number 112 When activated, psi monitor stays active for at least the duration of one 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/power/ |
| 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). 72 priority order of callbacks from high to low is: PM domain, device type, class [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/driver-api/usb/ |
| D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use 17 - Supports USB 2.0, for high speed devices which can stream data at 20 - Handles devices with dozens of endpoints just as well as ones with 21 just two fixed-function ones. Gadget drivers can be written so 24 - Flexible enough to expose more complex USB device capabilities such 28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the 29 Linux-USB host side. 31 - Sharing data structures and API models with the Linux-USB host side 32 API. This helps the OTG support, and looks forward to more-symmetric 36 - Minimalist, so it's easier to support new device controller hardware. [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/admin-guide/ |
| D | kernel-parameters.txt | 16 force -- enable ACPI if default was off 17 on -- enable ACPI but allow fallback to DT [arm64,riscv64] 18 off -- disable ACPI if default was on 19 noirq -- do not use ACPI for IRQ routing 20 strict -- Be less tolerant of platforms that are not 22 rsdt -- prefer RSDT over (default) XSDT 23 copy_dsdt -- copy DSDT to memory 24 nospcr -- disable console in ACPI SPCR table as 41 If set to vendor, prefer vendor-specific driver 73 Documentation/firmware-guide/acpi/debug.rst for more information about [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 …]
|