1 Specifying wakeup capability for devices
2 ============================================
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
11 as wake capable, then it is up to the device to determine which interrupts can
14 However if a device has a dedicated interrupt as the wakeup source, then it
15 needs to specify/identify it using a device specific interrupt name. In such
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
19 the canonical interrupt name.
21 List of legacy properties and respective binding document
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
27 Documentation/devicetree/bindings/mfd/tc3589x.txt
28 Documentation/devicetree/bindings/input/touchscreen/ads7846.txt
29 4. "linux,keypad-wakeup" Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
30 5. "linux,input-wakeup" Documentation/devicetree/bindings/input/samsung-keypad.txt
31 6. "nvidia,wakeup-source" Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt
36 1. With "wakeup" interrupt name
39 compatible = "vendor,device-id";
40 reg = <0x10000 0x1000>;
41 interrupts = <0 19 4>, <0 21 4>, <0 22 4>;
42 interrupt-names = "ack", "err", "wakeup";
46 2. Without "wakeup" interrupt name
49 compatible = "google,cros-ec-i2c";
52 interrupt-parent = <&gpx1>;
53 pinctrl-names = "default";
54 pinctrl-0 = <&ec_irq>;
61 compatible = "gpio-keys";
66 debounce-interval = <50>;
70 gpios = <&iofpga_gpio0 0 0x4>;