| /kernel/linux/linux-5.10/drivers/acpi/ |
| D | wakeup.c | 3 * wakeup.c - support wakeup devices
17 bool (*wakeup)(void *context); member
34 * Enable wakeup device power of devices with the state.enable flag set and set
35 * the wakeup enable mask bits in the GPE registers that correspond to wakeup
44 if (!dev->wakeup.flags.valid in acpi_enable_wakeup_devices()
45 || sleep_state > (u32) dev->wakeup.sleep_state in acpi_enable_wakeup_devices()
47 || dev->wakeup.prepare_count)) in acpi_enable_wakeup_devices()
54 acpi_set_gpe_wake_mask(dev->wakeup.gpe_device, dev->wakeup.gpe_number, in acpi_enable_wakeup_devices()
60 * acpi_disable_wakeup_devices - Disable devices' wakeup capability.
69 if (!dev->wakeup.flags.valid in acpi_disable_wakeup_devices()
[all …]
|
| D | device_pm.c | 460 if (adev->wakeup.flags.notifier_present) { in acpi_pm_notify_handler()
461 pm_wakeup_ws_event(adev->wakeup.ws, 0, acpi_s2idle_wakeup()); in acpi_pm_notify_handler()
462 if (adev->wakeup.context.func) { in acpi_pm_notify_handler()
464 adev->wakeup.context.func, in acpi_pm_notify_handler()
465 dev_name(adev->wakeup.context.dev)); in acpi_pm_notify_handler()
466 adev->wakeup.context.func(&adev->wakeup.context); in acpi_pm_notify_handler()
478 * @dev: Device to generate a wakeup event for while handling the notification.
481 * NOTE: @adev need not be a run-wake or wakeup device to be a valid source of
482 * PM wakeup events. For example, wakeup events may be generated for bridges
483 * if one of the devices below the bridge is signaling wakeup, even if the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-wakeup | 1 What: /sys/class/wakeup/
5 The /sys/class/wakeup/ directory contains pointers to all
6 wakeup sources in the kernel at that moment in time.
8 What: /sys/class/wakeup/.../name
12 This file contains the name of the wakeup source.
14 What: /sys/class/wakeup/.../active_count
18 This file contains the number of times the wakeup source was
21 What: /sys/class/wakeup/.../event_count
25 This file contains the number of signaled wakeup events
26 associated with the wakeup source.
[all …]
|
| /kernel/linux/linux-4.19/drivers/base/power/ |
| D | wakeup.c | 2 * drivers/base/power/wakeup.c - System wakeup events framework
29 * if wakeup events are registered during or immediately before the transition.
33 /* First wakeup IRQ seen by the kernel in the last cycle. */
40 * Combined counters of registered wakeup events and wakeup events in progress.
76 * wakeup_source_prepare - Prepare a new wakeup source for initialization.
77 * @ws: Wakeup source to prepare.
78 * @name: Pointer to the name of the new wakeup source.
94 * @name: Name of the new wakeup source.
111 * @ws: Wakeup source to prepare for destruction.
114 * be run in parallel with this function for the same wakeup source object.
[all …]
|
| /kernel/linux/linux-5.10/drivers/base/power/ |
| D | wakeup.c | 3 * drivers/base/power/wakeup.c - System wakeup events framework
32 * if wakeup events are registered during or immediately before the transition.
36 /* First wakeup IRQ seen by the kernel in the last cycle. */
43 * Combined counters of registered wakeup events and wakeup events in progress.
82 * @name: Name of the new wakeup source.
152 * @ws: Wakeup source to destroy.
154 * Use only for wakeup source objects created with wakeup_source_create().
168 * wakeup_source_add - Add given object to the list of wakeup sources.
169 * @ws: Wakeup source object to add to the list.
189 * wakeup_source_remove - Remove given object from the wakeup sources list.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/power/ |
| D | wakeup-source.txt | 1 Specifying wakeup capability for devices
6 Nodes that describe devices which has wakeup capability must contain an
7 "wakeup-source" boolean property.
9 Also, if device is marked as a wakeup source, then all the primary
10 interrupt(s) can be used as wakeup interrupt(s).
12 However if the devices have dedicated interrupt as the wakeup source
14 interrupt name. In such cases only that interrupt can be used as wakeup
20 1. "enable-sdio-wakeup" Documentation/devicetree/bindings/mmc/mmc.txt
21 2. "gpio-key,wakeup" Documentation/devicetree/bindings/input/gpio-keys{,-polled}.txt
23 4. "linux,wakeup" Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/ |
| D | wakeup-source.txt | 1 Specifying wakeup capability for devices
6 Nodes that describe devices which has wakeup capability must contain an
7 "wakeup-source" boolean property.
9 Also, if device is marked as a wakeup source, then all the primary
10 interrupt(s) can be used as wakeup interrupt(s).
12 However if the devices have dedicated interrupt as the wakeup source
14 interrupt name. In such cases only that interrupt can be used as wakeup
20 1. "enable-sdio-wakeup" Documentation/devicetree/bindings/mmc/mmc.txt
21 2. "gpio-key,wakeup" Documentation/devicetree/bindings/input/gpio-keys{,-polled}.txt
23 4. "linux,wakeup" Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
[all …]
|
| /kernel/linux/linux-4.19/drivers/acpi/ |
| D | wakeup.c | 3 * wakeup.c - support wakeup devices
27 * Enable wakeup device power of devices with the state.enable flag set and set
28 * the wakeup enable mask bits in the GPE registers that correspond to wakeup
39 if (!dev->wakeup.flags.valid in acpi_enable_wakeup_devices()
40 || sleep_state > (u32) dev->wakeup.sleep_state in acpi_enable_wakeup_devices()
42 || dev->wakeup.prepare_count)) in acpi_enable_wakeup_devices()
49 acpi_set_gpe_wake_mask(dev->wakeup.gpe_device, dev->wakeup.gpe_number, in acpi_enable_wakeup_devices()
55 * acpi_disable_wakeup_devices - Disable devices' wakeup capability.
66 if (!dev->wakeup.flags.valid in acpi_disable_wakeup_devices()
67 || sleep_state > (u32) dev->wakeup.sleep_state in acpi_disable_wakeup_devices()
[all …]
|
| D | device_pm.c | 413 if (adev->wakeup.flags.notifier_present) { in acpi_pm_notify_handler()
414 pm_wakeup_ws_event(adev->wakeup.ws, 0, acpi_s2idle_wakeup()); in acpi_pm_notify_handler()
415 if (adev->wakeup.context.func) { in acpi_pm_notify_handler()
417 adev->wakeup.context.func, in acpi_pm_notify_handler()
418 dev_name(adev->wakeup.context.dev)); in acpi_pm_notify_handler()
419 adev->wakeup.context.func(&adev->wakeup.context); in acpi_pm_notify_handler()
431 * @dev: Device to generate a wakeup event for while handling the notification.
434 * NOTE: @adev need not be a run-wake or wakeup device to be a valid source of
435 * PM wakeup events. For example, wakeup events may be generated for bridges
436 * if one of the devices below the bridge is signaling wakeup, even if the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | marvell-bt-8xxx.txt | 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
29 named "wakeup" from the interrupt-names and interrupt arrays.
32 bluetooth chip can wakeup host platform under certain
38 IRQ pin 119 is used as system wakeup source interrupt.
39 wakeup pin 13 and gap 100ms are configured so that firmware can wakeup host
40 using this device side pin and wakeup latency.
63 marvell,wakeup-pin = /bits/ 16 <0x0d>;
64 marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | marvell-bt-8xxx.txt | 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
29 named "wakeup" from the interrupt-names and interrupt arrays.
32 bluetooth chip can wakeup host platform under certain
38 IRQ pin 119 is used as system wakeup source interrupt.
39 wakeup pin 13 and gap 100ms are configured so that firmware can wakeup host
40 using this device side pin and wakeup latency.
63 marvell,wakeup-pin = /bits/ 16 <0x0d>;
64 marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 47 - st,wakeup-{x,y,z}-{lo,hi}: set wakeup condition on x/y/z axis for
49 - st,wakeup-threshold: set wakeup threshold
50 - st,wakeup2-{x,y,z}-{lo,hi}: set wakeup condition on x/y/z axis for
51 upper/lower limit for second wakeup
53 - st,wakeup2-threshold: set wakeup threshold for second wakeup
82 st,wakeup-x-lo;
83 st,wakeup-x-hi;
84 st,wakeup-y-lo;
85 st,wakeup-y-hi;
86 st,wakeup-z-lo;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 47 - st,wakeup-{x,y,z}-{lo,hi}: set wakeup condition on x/y/z axis for
49 - st,wakeup-threshold: set wakeup threshold
50 - st,wakeup2-{x,y,z}-{lo,hi}: set wakeup condition on x/y/z axis for
51 upper/lower limit for second wakeup
53 - st,wakeup2-threshold: set wakeup threshold for second wakeup
82 st,wakeup-x-lo;
83 st,wakeup-x-hi;
84 st,wakeup-y-lo;
85 st,wakeup-y-hi;
86 st,wakeup-z-lo;
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | ste-nomadik-pinctrl.dtsi | 56 ste,sleep-wakeup = <SLPM_WAKEUP_DISABLE>;
62 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
68 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
75 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
81 ste,sleep-wakeup = <SLPM_WAKEUP_DISABLE>;
88 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
95 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
102 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
109 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
115 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | ste-nomadik-pinctrl.dtsi | 55 ste,sleep-wakeup = <SLPM_WAKEUP_DISABLE>;
61 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
67 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
74 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
80 ste,sleep-wakeup = <SLPM_WAKEUP_DISABLE>;
87 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
94 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
101 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
108 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
114 ste,sleep-wakeup = <SLPM_WAKEUP_ENABLE>;
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pm_wakeup.h | 3 * pm_wakeup.h - Power management wakeup interface
21 * struct wakeup_source - Representation of wakeup sources
23 * @name: Name of the wakeup source
24 * @id: Wakeup source id
25 * @entry: Wakeup source list entry
26 * @lock: Wakeup source lock
28 * @timer: Wakeup timer list
29 * @timer_expires: Wakeup timer expiration
30 * @total_time: Total time this wakeup source has been active.
31 * @max_time: Maximum time this wakeup source has been continuously active.
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | pm_wakeup.h | 2 * pm_wakeup.h - Power management wakeup interface
34 * struct wakeup_source - Representation of wakeup sources
36 * @name: Name of the wakeup source
37 * @entry: Wakeup source list entry
38 * @lock: Wakeup source lock
40 * @timer: Wakeup timer list
41 * @timer_expires: Wakeup timer expiration
42 * @total_time: Total time this wakeup source has been active.
43 * @max_time: Maximum time this wakeup source has been continuously active.
44 * @last_time: Monotonic clock when the wakeup source's was touched last time.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | suspend-and-interrupts.txt | 56 System Wakeup Interrupts, enable_irq_wake() and disable_irq_wake()
59 System wakeup interrupts generally need to be configured to wake up the system
65 during system sleep so as to trigger a system wakeup when needed. For example,
67 handling system wakeup events. Then, if a given interrupt line is supposed to
70 After wakeup, it generally is better to disable that input to prevent the
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
84 of the points where the suspend thread looks for pending wakeup events).
86 This way every interrupt from a wakeup interrupt source will either cause the
89 not executed for system wakeup IRQs. They are only executed for IRQF_NO_SUSPEND
90 IRQs at that time, but those IRQs should not be configured for system wakeup
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | samsung-pinctrl.txt | 41 wakeup-interrupt-controller {
42 compatible = "samsung,exynos7-wakeup-eint";
117 External GPIO and Wakeup Interrupts:
120 is the external gpio interrupt and second is the external wakeup interrupts.
121 The difference between the two is that the external wakeup interrupts can be
122 used as system wakeup events.
144 B. External Wakeup Interrupts: For supporting external wakeup interrupts, a
145 child node representing the external wakeup interrupt controller should be
148 Only one pin-controller device node can include external wakeup interrupts
149 child node (in other words, only one External Wakeup Interrupts
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | samsung-pinctrl.txt | 41 wakeup-interrupt-controller {
42 compatible = "samsung,exynos7-wakeup-eint";
117 External GPIO and Wakeup Interrupts:
120 is the external gpio interrupt and second is the external wakeup interrupts.
121 The difference between the two is that the external wakeup interrupts can be
122 used as system wakeup events.
144 B. External Wakeup Interrupts: For supporting external wakeup interrupts, a
145 child node representing the external wakeup interrupt controller should be
148 Only one pin-controller device node can include external wakeup interrupts
149 child node (in other words, only one External Wakeup Interrupts
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | suspend-and-interrupts.rst | 58 System Wakeup Interrupts, enable_irq_wake() and disable_irq_wake()
61 System wakeup interrupts generally need to be configured to wake up the system
67 during system sleep so as to trigger a system wakeup when needed. For example,
69 handling system wakeup events. Then, if a given interrupt line is supposed to
72 After wakeup, it generally is better to disable that input to prevent the
77 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
86 of the points where the suspend thread looks for pending wakeup events).
88 This way every interrupt from a wakeup interrupt source will either cause the
91 not executed for system wakeup IRQs. They are only executed for IRQF_NO_SUSPEND
92 IRQs at that time, but those IRQs should not be configured for system wakeup
[all …]
|
| /kernel/linux/linux-4.19/Documentation/usb/ |
| D | chipidea.txt | 77 2. How to enable USB as system wakeup source
79 Below is the example for how to enable USB as system wakeup source
82 2.1 Enable core's wakeup
83 echo enabled > /sys/bus/platform/devices/ci_hdrc.0/power/wakeup
84 2.2 Enable glue layer's wakeup
85 echo enabled > /sys/bus/platform/devices/2184000.usb/power/wakeup
86 2.3 Enable PHY's wakeup (optional)
87 echo enabled > /sys/bus/platform/devices/20c9000.usbphy/power/wakeup
88 2.4 Enable roothub's wakeup
89 echo enabled > /sys/bus/usb/devices/usb1/power/wakeup
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-imx/ |
| D | mach-pcm037_eet.c | 70 .wakeup = 0,
76 .wakeup = 0,
82 .wakeup = 0,
88 .wakeup = 0,
94 .wakeup = 0,
100 .wakeup = 0,
106 .wakeup = 0,
112 .wakeup = 0,
118 .wakeup = 0,
124 .wakeup = 0,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | chipidea.rst | 105 2. How to enable USB as system wakeup source
107 Below is the example for how to enable USB as system wakeup source
110 2.1 Enable core's wakeup::
112 echo enabled > /sys/bus/platform/devices/ci_hdrc.0/power/wakeup
114 2.2 Enable glue layer's wakeup::
116 echo enabled > /sys/bus/platform/devices/2184000.usb/power/wakeup
118 2.3 Enable PHY's wakeup (optional)::
120 echo enabled > /sys/bus/platform/devices/20c9000.usbphy/power/wakeup
122 2.4 Enable roothub's wakeup::
124 echo enabled > /sys/bus/usb/devices/usb1/power/wakeup
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-power | 172 concurrent arrival of wakeup events. Reading from it returns
173 the current number of registered wakeup events and it blocks if
174 some wakeup events are being processed at the time the file is
176 number of wakeup events is equal to the written value and, if
178 to a sleep state if any wakeup events are reported after the
203 attempt will only succeed if there are no active wakeup sources
217 wakeup source objects and activate them on demand (if one of
218 those wakeup sources is active, reads from the
221 it will be assumed to represent a wakeup source name. If there
222 is a wakeup source object with that name, it will be activated
[all …]
|