Home
last modified time | relevance | path

Searched +full:wakeup +full:- +full:source (Results 1 – 25 of 1099) sorted by relevance

12345678910>>...44

/kernel/linux/linux-4.19/drivers/base/power/
Dwakeup.c2 * 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.
47 #define MAX_IN_PROGRESS ((1 << IN_PROGRESS_BITS) - 1)
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.
87 ws->name = name; in wakeup_source_prepare()
93 * wakeup_source_create - Create a struct wakeup_source object.
[all …]
/kernel/linux/linux-5.10/drivers/base/power/
Dwakeup.c1 // SPDX-License-Identifier: GPL-2.0
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.
50 #define MAX_IN_PROGRESS ((1 << IN_PROGRESS_BITS) - 1)
81 * wakeup_source_create - Create a struct wakeup_source object.
82 * @name: Name of the new wakeup source.
97 ws->name = ws_name; in wakeup_source_create()
102 ws->id = id; in wakeup_source_create()
[all …]
Dwakeup_stats.c1 // SPDX-License-Identifier: GPL-2.0
3 * Wakeup statistics in sysfs
6 * Copyright (c) 2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
29 return sysfs_emit(buf, "%lu\n", ws->_name); \
43 ws->active ? ktime_sub(ktime_get(), ws->last_time) : 0; in active_time_ms_show()
54 ktime_t total_time = ws->total_time; in total_time_ms_show()
56 if (ws->active) { in total_time_ms_show()
57 active_time = ktime_sub(ktime_get(), ws->last_time); in total_time_ms_show()
70 ktime_t max_time = ws->max_time; in max_time_ms_show()
72 if (ws->active) { in max_time_ms_show()
[all …]
/kernel/linux/linux-5.10/include/linux/
Dpm_wakeup.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
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.
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/power/
Dwakeup-source.txt1 Specifying wakeup capability for devices
5 ----------------
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
18 ---------------------------------------------------------
20 1. "enable-sdio-wakeup" Documentation/devicetree/bindings/mmc/mmc.txt
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Dwakeup-source.txt1 Specifying wakeup capability for devices
5 ----------------
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
18 ---------------------------------------------------------
20 1. "enable-sdio-wakeup" Documentation/devicetree/bindings/mmc/mmc.txt
[all …]
/kernel/linux/linux-4.19/include/linux/
Dpm_wakeup.h2 * pm_wakeup.h - Power management wakeup interface
19 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
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.
[all …]
/kernel/linux/linux-4.19/Documentation/ABI/testing/
Dsysfs-power15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
50 'firmware' - means that the memory image will be saved to disk
53 'platform' - the memory image will be saved by the kernel and
56 'shutdown' - the memory image will be saved by the kernel and
58 'reboot' - the memory image will be saved by the kernel and
62 two testing modes of the suspend-to-disk mechanism: 'testproc'
[all …]
/kernel/linux/linux-4.19/Documentation/power/
Dsuspend-and-interrupts.txt8 -----------------------------------
12 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
27 Device IRQs are re-enabled during system resume, right before the "early" phase
28 of resuming devices (that is, before starting to execute ->resume_early
33 ------------------------
36 suspend-resume cycle, including the "noirq" phases of suspending and resuming
39 but also to IPIs and to some other special-purpose interrupts.
42 requesting a special-purpose interrupt. It causes suspend_device_irqs() to
44 expected during the suspend-resume cycle, but does not guarantee that the
45 interrupt will wake the system from a suspended state -- for such cases it is
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/rtc/
Disil,isl12057.txt8 ("wakeup-source") to handle the specific use-case found
9 on at least three in-tree users of the chip (NETGEAR ReadyNAS 102, 104
10 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip
13 RTC alarm rings. In order to mark the device has a wakeup source and
20 - "compatible": must be "isil,isl12057"
21 - "reg": I2C bus address of the device
25 - "wakeup-source": mark the chip as a wakeup source, independently of
38 that the pinctrl-related properties below are given for completeness and
41 "interrupt-parent" and "interrupts" are usually sufficient):
60 pinctrl-0 = <&rtc_alarm_pin>;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/
Disil,isl12057.txt8 ("wakeup-source") to handle the specific use-case found
9 on at least three in-tree users of the chip (NETGEAR ReadyNAS 102, 104
10 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip
13 RTC alarm rings. In order to mark the device has a wakeup source and
20 - "compatible": must be "isil,isl12057"
21 - "reg": I2C bus address of the device
25 - "wakeup-source": mark the chip as a wakeup source, independently of
38 that the pinctrl-related properties below are given for completeness and
41 "interrupt-parent" and "interrupts" are usually sufficient):
60 pinctrl-0 = <&rtc_alarm_pin>;
[all …]
/kernel/linux/linux-5.10/Documentation/power/
Dsuspend-and-interrupts.rst10 -----------------------------------
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 …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-power15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
51 'firmware' - means that the memory image will be saved to disk
55 'platform' - the memory image will be saved by the kernel and
59 'shutdown' - the memory image will be saved by the kernel and
62 'reboot' - the memory image will be saved by the kernel and
66 two testing modes of the suspend-to-disk mechanism: 'testproc'
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/
Dcypress,cyapa.txt4 - compatible: must be "cypress,cyapa".
5 - reg: I2C address of the chip.
6 - interrupts: interrupt to which the chip is connected (see interrupt
10 - wakeup-source: touchpad can be used as a wakeup source.
11 - pinctrl-names: should be "default" (see pinctrl binding [1]).
12 - pinctrl-0: a phandle pointing to the pin settings for the device (see
14 - vcc-supply: a phandle for the regulator supplying 3.3V power.
16 [0]: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
17 [1]: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
27 interrupt-parent = <&gpio>;
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/input/
Dcypress,cyapa.txt4 - compatible: must be "cypress,cyapa".
5 - reg: I2C address of the chip.
6 - interrupts: interrupt to which the chip is connected (see interrupt
10 - wakeup-source: touchpad can be used as a wakeup source.
11 - pinctrl-names: should be "default" (see pinctrl binding [1]).
12 - pinctrl-0: a phandle pointing to the pin settings for the device (see
14 - vcc-supply: a phandle for the regulator supplying 3.3V power.
16 [0]: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
17 [1]: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
27 interrupt-parent = <&gpio>;
[all …]
/kernel/linux/linux-5.10/drivers/soc/fsl/
Drcpm.c1 // SPDX-License-Identifier: GPL-2.0
3 // rcpm.c - Freescale QorIQ RCPM driver
26 * rcpm_pm_prepare - performs device-level tasks associated with power
27 * management, such as programming related to the wakeup source control.
37 struct device_node *np = dev->of_node; in rcpm_pm_prepare()
43 return -EINVAL; in rcpm_pm_prepare()
45 base = rcpm->ippdexpcr_base; in rcpm_pm_prepare()
48 /* Begin with first registered wakeup source */ in rcpm_pm_prepare()
52 if (!ws->dev || !ws->dev->parent) in rcpm_pm_prepare()
55 ret = device_property_read_u32_array(ws->dev->parent, in rcpm_pm_prepare()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/
Dst,stm32-ipcc.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/mailbox/st,stm32-ipcc.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
16 - Fabien Dessenne <fabien.dessenne@st.com>
17 - Arnaud Pouliquen <arnaud.pouliquen@st.com>
21 const: st,stm32mp1-ipcc
31 - description: rx channel occupied
32 - description: tx channel free
33 - description: wakeup source
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Domap3-pandora-common.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
9 #include <dt-bindings/input/input.h>
14 cpu0-supply = <&vcc>;
29 #clock-cells = <0>;
30 compatible = "fixed-clock";
31 clock-frequency = <26000000>;
35 compatible = "connector-analog-tv";
40 remote-endpoint = <&venc_out>;
45 gpio-leds {
47 compatible = "gpio-leds";
[all …]
Domap3-ldp.dts1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2013 Texas Instruments Incorporated - https://www.ti.com/
5 /dts-v1/;
7 #include <dt-bindings/input/input.h>
9 #include "omap-gpmc-smsc911x.dtsi"
13 compatible = "ti,omap3-ldp", "ti,omap3430", "ti,omap3";
22 cpu0-supply = <&vcc>;
27 compatible = "gpio-keys";
28 pinctrl-names = "default";
29 pinctrl-0 = <&gpio_key_pins>;
[all …]
Demev2-kzm9d.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the KZM9D board
7 /dts-v1/;
10 #include <dt-bindings/gpio/gpio.h>
11 #include <dt-bindings/input/input.h>
12 #include <dt-bindings/interrupt-controller/irq.h>
29 stdout-path = "serial1:115200n8";
33 compatible = "gpio-keys";
35 debounce-interval = <50>;
36 wakeup-source;
[all …]
/kernel/linux/linux-4.19/arch/arm/boot/dts/
Domap3-pandora-common.dtsi12 #include <dt-bindings/input/input.h>
17 cpu0-supply = <&vcc>;
32 #clock-cells = <0>;
33 compatible = "fixed-clock";
34 clock-frequency = <26000000>;
38 compatible = "connector-analog-tv";
43 remote-endpoint = <&venc_out>;
48 gpio-leds {
50 compatible = "gpio-leds";
52 pinctrl-names = "default";
[all …]
Domap3-ldp.dts2 * Copyright (C) 2013 Texas Instruments Incorporated - http://www.ti.com/
8 /dts-v1/;
10 #include <dt-bindings/input/input.h>
12 #include "omap-gpmc-smsc911x.dtsi"
16 compatible = "ti,omap3-ldp", "ti,omap3";
25 cpu0-supply = <&vcc>;
30 compatible = "gpio-keys";
31 pinctrl-names = "default";
32 pinctrl-0 = <&gpio_key_pins>;
38 wakeup-source;
[all …]
Demev2-kzm9d.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the KZM9D board
7 /dts-v1/;
10 #include <dt-bindings/gpio/gpio.h>
11 #include <dt-bindings/input/input.h>
12 #include <dt-bindings/interrupt-controller/irq.h>
29 stdout-path = "serial1:115200n8";
33 compatible = "gpio-keys";
35 debounce-interval = <50>;
36 wakeup-source;
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/i2c/
Di2c.txt8 -------------------
10 - #address-cells - should be <1>. Read more about addresses below.
11 - #size-cells - should be <0>.
12 - compatible - name of I2C bus controller following generic names
27 -------------------
32 - clock-frequency
35 - i2c-bus
37 devices and non-I2C devices, the 'i2c-bus' subnode can be used for
38 populating I2C devices. If the 'i2c-bus' subnode is present, only
40 '#address-cells' and '#size-cells' must be defined under this subnode
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/soc/fsl/
Drcpm.txt2 -------------------------------------------
3 The RCPM performs all device-level tasks associated with device run control
7 - reg : Offset and length of the register set of the RCPM block.
8 - fsl,#rcpm-wakeup-cells : The number of IPPDEXPCR register cells in the
9 fsl,rcpm-wakeup property.
10 - compatible : Must contain a chip-specific RCPM block compatible string
11 and (if applicable) may contain a chassis-version RCPM compatible
12 string. Chip-specific strings are of the form "fsl,<chip>-rcpm",
14 * "fsl,p2041-rcpm"
15 * "fsl,p5020-rcpm"
[all …]

12345678910>>...44