bindings/power/wakeup-source.txt

1 Specifying wakeup capability for devices
5 ----------------
6 Nodes that describe devices which have wakeup capability may contain a
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
14 However if a device has a dedicated interrupt as the wakeup source, then it
16 cases only that interrupt can be used as a wakeup interrupt.
18 While various legacy interrupt names exist, new devices should use "wakeup" as
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
28 				Documentation/devicetree/bindings/input/touchscreen/ti,ads7843.yaml
29 4. "linux,keypad-wakeup"	Documentation/devicetree/bindings/input/qcom,pm8921-keypad.yaml
30 5. "linux,input-wakeup"		Documentation/devicetree/bindings/input/samsung,s3c6410-keypad.yaml
31 6. "nvidia,wakeup-source"	Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt
34 --------
36 1. With "wakeup" interrupt name
39 		compatible	= "vendor,device-id";
42 		interrupt-names	= "ack", "err", "wakeup";
43 		wakeup-source;
46 2. Without "wakeup" interrupt name
48 	embedded-controller {
49 		compatible = "google,cros-ec-i2c";
52 		interrupt-parent = <&gpx1>;
53 		pinctrl-names = "default";
54 		pinctrl-0 = <&ec_irq>;
55 		wakeup-source;
61 		compatible = "gpio-keys";
62 		#address-cells = <1>;
63 		#size-cells = <0>;
66 			debounce-interval = <50>;
67 			wakeup-source;