Home
last modified time | relevance | path

Searched refs:wake (Results 1 – 25 of 276) sorted by relevance

12345678910>>...12

/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-devices-platform-ACPI-TAD29 "disabled", if the AC alarm is not set to wake up the system.
35 expires, it will immediately wake up the system from the S3
43 (RW) The AC alarm expired timer wake policy (see ACPI 6.2,
46 Reads return the current expired timer wake delay for the AC
50 Write a new expired timer wake delay for the AC alarm timer in
51 seconds or "never" to it to set the expired timer wake delay for
52 the AC alarm timer or to set its expired wake policy to discard
77 it will immediately wake up the system from the S3 sleep state
96 (RW,optional) The DC alarm expired timer wake policy.
Dsysfs-devices-power14 space to check if the device is enabled to wake up the system
33 be enabled to wake up the system from sleep states.
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
111 is not capable to wake up the system from sleep states, this
112 attribute is not present. If the device is not enabled to wake
122 read-only. If the device is not capable to wake up the system
124 device is not enabled to wake up the system from sleep states,
[all …]
Dsysfs-class-chromeos11 Control the keyboard wake lid angle. Values are between
12 0 and 360. This file will also show the keyboard wake lid
/Linux-v5.4/Documentation/devicetree/bindings/rtc/
Dbrcm,brcmstb-waketimer.txt1 Broadcom STB wake-up Timer
3 The Broadcom STB wake-up timer provides a 27Mhz resolution timer, with the
4 ability to wake up the system from low-power suspend/standby modes.
Drtc-meson-vrtc.txt15 the SCP will wake up and will then wake the AP.
/Linux-v5.4/Documentation/devicetree/bindings/net/wireless/
Dbrcm,bcm43xx-fmac.txt14 - interrupts : specifies attributes for the out-of-band interrupt (host-wake).
17 to "host-wake".
36 interrupt-names = "host-wake";
/Linux-v5.4/drivers/rtc/
Drtc-bd70528.c218 struct bd70528_rtc_wake wake; in bd70528_set_alarm() local
225 &wake, sizeof(wake)); in bd70528_set_alarm()
239 tmday2rtc(&a->time, &wake.time); in bd70528_set_alarm()
243 wake.ctrl |= BD70528_MASK_WAKE_EN; in bd70528_set_alarm()
246 wake.ctrl &= ~BD70528_MASK_WAKE_EN; in bd70528_set_alarm()
250 BD70528_REG_RTC_WAKE_START, &wake, in bd70528_set_alarm()
251 sizeof(wake)); in bd70528_set_alarm()
/Linux-v5.4/Documentation/devicetree/bindings/arm/
Datmel-sysregs.txt90 - #address-cells: should be one. The cell is the wake-up input index.
95 - debounce-delay-us: minimum wake-up inputs debouncer period in
97 - atmel,wakeup-rtc-timer: boolean to enable Real-Time Clock wake-up.
102 The node contains child nodes for each wake-up input that the platform uses.
107 Tree. Note also that input 0 is linked to the wake-up pin and is frequently
111 - reg: should contain the wake-up input index [0 - 15].
114 - atmel,wakeup-active-high: boolean, the corresponding wake-up input described
115 by the child, forces the wake-up of the core power supply on a high level.
/Linux-v5.4/Documentation/devicetree/bindings/net/can/
Dtcan4x5x.txt13 - device-wake-gpios: Wake up GPIO to wake up the TCAN device.
38 device-wake-gpios = <&gpio1 15 GPIO_ACTIVE_HIGH>;
/Linux-v5.4/tools/perf/bench/
DBuild5 perf-y += futex-wake.o
6 perf-y += futex-wake-parallel.o
/Linux-v5.4/Documentation/admin-guide/
Dbtmrvl.rst17 where GPIO is the pin number of GPIO used to wake up the host.
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:
54 These commands are used to enable host sleep or wake up firmware
/Linux-v5.4/Documentation/devicetree/bindings/input/
Dgpio-keys.txt27 - wakeup-source: Boolean, button can wake-up the system.
29 - wakeup-event-action: Specifies whether the key should wake the
31 only valid for keys that wake up the system (e.g., when the
/Linux-v5.4/Documentation/devicetree/bindings/serial/
Dst,stm32-usart.txt12 - An optional wake-up interrupt.
24 - interrupt-names, if optional wake-up interrupt is used, should be:
26 - "wakeup" the name for the optional wake-up interrupt
/Linux-v5.4/arch/arm/boot/dts/
Drk3288-veyron.dtsi33 * ugly GPIO key to allow Bluetooth to wake from S3.
42 bt-wake {
459 snps,need-phy-for-wake;
468 snps,need-phy-for-wake;
486 /* Common for sleep and wake, but no owners */
495 /* Common for sleep and wake, but no owners */
585 bt_host_wake: bt-host-wake {
589 bt_host_wake_l: bt-host-wake-l {
618 bt_dev_wake_sleep: bt-dev-wake-sleep {
622 bt_dev_wake_awake: bt-dev-wake-awake {
Drk3288-veyron-chromebook.dtsi140 /* Common for sleep and wake, but no owners */
150 /* Common for sleep and wake, but no owners */
179 suspend_l_wake: suspend-l-wake {
/Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/
Darm,vic.txt26 configured as wake up source for the system. Order of bits is the same as for
28 configured as a wake up source for the system. If unspecied, defaults to all
29 interrupt sources configurable as wake up sources.
/Linux-v5.4/Documentation/
Dfutex-requeue-pi.txt20 implementation would wake the highest-priority waiter, and leave the
92 The requeue code cannot simply wake the waiter and leave it to
109 wake-up scenarios.
113 possibly wake the waiting tasks. Internally, this system call is
125 their sum is all that really matters. futex_requeue() will wake or
126 requeue up to nr_wake + nr_requeue tasks. It will wake only as many
/Linux-v5.4/drivers/nfc/s3fwrn5/
Ds3fwrn5.h63 static inline int s3fwrn5_set_wake(struct s3fwrn5_info *info, bool wake) in s3fwrn5_set_wake() argument
68 info->phy_ops->set_wake(info->phy_id, wake); in s3fwrn5_set_wake()
/Linux-v5.4/tools/perf/Documentation/
Dperf-bench.txt197 *wake*::
198 Suite for evaluating wake calls.
200 *wake-parallel*::
201 Suite for evaluating parallel wake calls.
/Linux-v5.4/kernel/rcu/
Dtree_exp.h188 bool wake, unsigned long flags) in __rcu_report_exp_rnp() argument
203 if (wake) { in __rcu_report_exp_rnp()
222 static void __maybe_unused rcu_report_exp_rnp(struct rcu_node *rnp, bool wake) in rcu_report_exp_rnp() argument
227 __rcu_report_exp_rnp(rnp, wake, flags); in rcu_report_exp_rnp()
235 unsigned long mask, bool wake) in rcu_report_exp_cpu_mult() argument
245 __rcu_report_exp_rnp(rnp, wake, flags); /* Releases rnp->lock. */ in rcu_report_exp_cpu_mult()
/Linux-v5.4/Documentation/devicetree/bindings/input/touchscreen/
Dchipone_icn8318.txt7 - wake-gpios : GPIO specification for the WAKE input
36 wake-gpios = <&pio 1 3 GPIO_ACTIVE_HIGH>; /* PB3 */
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dbtusb.txt23 that shall be used for out-of-band wake-on-bt. Driver will
31 Following example uses irq pin number 3 of gpio0 for out of band wake-on-bt:
/Linux-v5.4/kernel/power/
Dsuspend.c134 if (s2idle_ops && s2idle_ops->wake) in s2idle_loop()
135 s2idle_ops->wake(); in s2idle_loop()
268 } else if (suspend_ops->wake) { in platform_resume_noirq()
269 suspend_ops->wake(); in platform_resume_noirq()
/Linux-v5.4/drivers/md/
Ddm-kcopyd.c206 static void wake(struct dm_kcopyd_client *kc) in wake() function
530 wake(kc); in complete_io()
543 wake(kc); in complete_io()
624 wake(kc); in process_jobs()
686 wake(kc); in dispatch_job()
754 wake(kc); in segment_complete()
890 wake(kc); in dm_kcopyd_do_callback()
/Linux-v5.4/Documentation/devicetree/bindings/usb/
Ddwc2.txt45 - snps,need-phy-for-wake: If present indicates that the phy needs to be left
47 - snps,reset-phy-on-wake: If present indicates that we need to reset the PHY when
63 snps,need-phy-for-wake;

12345678910>>...12