Searched +full:wake +full:- +full:up (Results 1 – 25 of 138) sorted by relevance
123456
| /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 …]
|
| 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/pinctrl/ |
| D | samsung,pinctrl-wakeup-interrupt.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S3C/S5P/Exynos SoC pin controller - wake-up interrupt controller
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
18 External wake-up interrupts for Samsung S3C/S5P/Exynos SoC pin controller.
19 For S3C24xx, S3C64xx, S5PV210 and Exynos4210 compatible wake-up interrupt
[all …]
|
| D | samsung,pinctrl-gpio-bank.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/samsung,pinctrl-gpio-bank.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S3C/S5P/Exynos SoC pin controller - gpio bank
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
24 '#gpio-cells':
27 gpio-controller: true
[all …]
|
| D | samsung,pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
22 - External GPIO interrupts (see interrupts property in pin controller node);
24 - External wake-up interrupts - multiplexed (capable of waking up the system
25 see interrupts property in external wake-up interrupt controller node -
26 samsung,pinctrl-wakeup-interrupt.yaml);
[all …]
|
| D | ste,nomadik.txt | 4 - compatible: "stericsson,db8500-pinctrl", "stericsson,db8540-pinctrl",
5 "stericsson,stn8815-pinctrl"
6 - nomadik-gpio-chips: array of phandles to the corresponding GPIO chips
8 - prcm: phandle to the PRCMU managing the back end of this pin controller
10 Please refer to pinctrl-bindings.txt in this directory for details of the
18 parameters, such as input, output, pull up, pull down...
23 (see pinctrl-bindings.txt):
26 - function: A string containing the name of the function to mux to the
28 - groups : An array of strings. Each string contains the name of a pin
30 set-up.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-power | 14 space to check if the device is enabled to wake up the system
33 be enabled to wake up the system from sleep states.
40 space to control the run-time power management of the device.
52 the device is suspended causes it to be woken up.
61 with the main suspend/resume thread) during system-wide power
86 attribute is read-only. If the device is not capable to wake up
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
100 the device is not enabled to wake up the system from sleep
110 state in progress. This attribute is read-only. If the device
[all …]
|
| D | sysfs-driver-intel-rapid-start | 1 What: /sys/bus/acpi/intel-rapid-start/wakeup_events
6 1: Wake to enter hibernation when the wakeup timer expires
7 2: Wake to enter hibernation when the battery reaches a
11 indicates that the system will wake to enter hibernation when
15 What: /sys/bus/acpi/intel-rapid-start/wakeup_time
20 remain asleep before waking up to enter hibernation.
|
| /Documentation/devicetree/bindings/net/can/ |
| D | tcan4x5x.txt | 7 - compatible:
11 - reg: 0
12 - #address-cells: 1
13 - #size-cells: 0
14 - spi-max-frequency: Maximum frequency of the SPI bus the chip can
16 - interrupt-parent: the phandle to the interrupt controller which provides
18 - interrupts: interrupt specification for data-ready.
24 - reset-gpios: Hardwired output GPIO. If not defined then software
26 - device-state-gpios: Input GPIO that indicates if the device is in
29 - device-wake-gpios: Wake up GPIO to wake up the TCAN device. Not
[all …]
|
| /Documentation/admin-guide/ |
| D | btmrvl.rst | 14 bit 8:0 -- Gap
15 bit 16:8 -- GPIO
17 where GPIO is the pin number of GPIO used to wake up the host.
18 It could be any valid GPIO pin# (e.g. 0-7) or 0xff (SDIO interface
26 # Use SDIO interface to wake up the host and set GAP to 0x80:
30 # Use GPIO pin #3 to wake up the host and set GAP to 0xff:
39 1 -- Enable auto sleep mode
40 0 -- Disable auto sleep mode
54 These commands are used to enable host sleep or wake up firmware
58 1 -- Enable host sleep
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | brcm,brcmstb-waketimer.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rtc/brcm,brcmstb-waketimer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom STB wake-up Timer
10 - Florian Fainelli <f.fainelli@gmail.com>
13 The Broadcom STB wake-up timer provides a 27Mhz resolution timer, with the
14 ability to wake up the system from low-power suspend/standby modes and
18 - $ref: rtc.yaml#
22 const: brcm,brcmstb-waketimer
[all …]
|
| D | amlogic,meson-vrtc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rtc/amlogic,meson-vrtc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Neil Armstrong <neil.armstrong@linaro.org>
17 application processors (AP) and the secure co-processor (SCP.) When
19 program an always-on timer before going sleep. When the timer expires,
20 the SCP will wake up and will then wake the AP.
23 - $ref: rtc.yaml#
28 - amlogic,meson-vrtc
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/arm,vic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 be nested or have the outputs wire-OR'd together.
18 - $ref: /schemas/interrupt-controller.yaml#
23 - arm,pl190-vic
24 - arm,pl192-vic
25 - arm,versatile-vic
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | atmel,maxtouch.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nick Dyer <nick@shmanahar.org>
11 - Linus Walleij <linus.walleij@linaro.org>
18 - $ref: input.yaml#
30 vdda-supply:
34 vdd-supply:
38 reset-gpios:
45 wake-gpios:
[all …]
|
| D | gpio-keys.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 - gpio-keys
16 - gpio-keys-polled
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
35 - items:
[all …]
|
| /Documentation/locking/ |
| D | futex-requeue-pi.rst | 5 Requeueing of tasks from a non-PI futex to a PI futex requires
8 boosting logic [see rt-mutex-design.rst] For the purposes of
14 ----------
19 gets to run first in classic thundering-herd formation. An ideal
20 implementation would wake the highest-priority waiter, and leave the
29 lock(cond->__data.__lock);
32 unlock(cond->__data.__lock);
33 futex_wait(cond->__data.__futex);
34 lock(cond->__data.__lock);
36 unlock(cond->__data.__lock);
[all …]
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 2 Notes on Power-Saving Mode
5 AC97 and HD-audio drivers have the automatic power-saving mode.
9 With the automatic power-saving, the driver turns off the codec power
15 The time-out for automatic power-off can be specified via ``power_save``
16 module option of snd-ac97-codec and snd-hda-intel modules. Specify
17 the time-out value in seconds. 0 means to disable the automatic
18 power-saving. The default value of timeout is given via
27 automatic power-save mode with 10 seconds, write to
35 state. Also, it often takes certain time to wake up from the
36 power-down to the active state. These are often hardly to fix, so
[all …]
|
| /Documentation/devicetree/bindings/timer/ |
| D | riscv,timer.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V timer
10 - Anup Patel <anup@brainfault.org>
13 RISC-V platforms always have a RISC-V timer device for the supervisor-mode
14 based on the time CSR defined by the RISC-V privileged specification. The
15 timer interrupts of this device are configured using the RISC-V SBI Time
16 extension or the RISC-V Sstc extension.
18 The clock frequency of RISC-V timer device is specified via the
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | smsc,lan9115.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Smart Mixed-Signal Connectivity (SMSC) LAN911x/912x Controller
10 - Shawn Guo <shawnguo@kernel.org>
13 - $ref: ethernet-controller.yaml#
18 - const: smsc,lan9115
19 - items:
20 - enum:
21 - smsc,lan89218
[all …]
|
| D | fsl-tsec-phy.txt | 5 the definition of the PHY node in booting-without-of.txt for an example
9 - reg : Offset and length of the register set for the device, and optionally
14 - compatible : Should define the compatible device type for the
16 - "fsl,gianfar-tbi"
17 - "fsl,gianfar-mdio"
18 - "fsl,etsec2-tbi"
19 - "fsl,etsec2-mdio"
20 - "fsl,ucc-mdio"
21 - "fsl,fman-mdio"
23 - "gianfar"
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | wakeup-source.txt | 5 ----------------
7 "wakeup-source" boolean property.
9 If the device is marked as a wakeup-source, interrupt wake capability depends
10 on the device specific "interrupt-names" property. If no interrupts are labeled
11 as wake capable, then it is up to the device to determine which interrupts can
12 wake the system.
22 ---------------------------------------------------------
24 1. "gpio-key,wakeup" Documentation/devicetree/bindings/input/gpio-keys{,-polled}.txt
25 2. "has-tpo" Documentation/devicetree/bindings/rtc/rtc-opal.txt
26 3. "linux,wakeup" Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
[all …]
|
| /Documentation/tools/rtla/ |
| D | common_timerlat_description.rst | 2 *timerlat* tracer dispatches a kernel thread per-cpu. These threads
3 set a periodic timer to wake themselves up and go back to sleep. After
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 12 take the runqueue lock. This is usually due to a wake up operation in
52 need an interrupt to wake them up when need_resched goes high.
57 - 5a. If TIF_POLLING_NRFLAG is set, and we do decide to enter
71 sparc - IRQs on at this point(?), change local_irq_save to _disable.
72 - TODO: needs secondary CPUs to disable preempt (See #1)
|
| /Documentation/power/ |
| D | suspend-and-interrupts.rst | 10 -----------------------------------
14 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
29 Device IRQs are re-enabled during system resume, right before the "early" phase
30 of resuming devices (that is, before starting to execute ->resume_early
35 ------------------------
38 suspend-resume cycle, including the "noirq" phases of suspending and resuming
41 but also to IPIs and to some other special-purpose interrupts.
44 requesting a special-purpose interrupt. It causes suspend_device_irqs() to
46 expected during the suspend-resume cycle, but does not guarantee that the
47 interrupt will wake the system from a suspended state -- for such cases it is
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | gpio-ir-receiver.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/media/gpio-ir-receiver.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
13 - $ref: rc.yaml#
17 const: gpio-ir-receiver
22 linux,autosuspend-period:
26 wakeup-source:
27 description: IR receiver can wake-up the system.
[all …]
|
123456