From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffy Chen Subject: [PATCH v2 2/3] Input: gpio-keys - allow setting wakeup event action in DT Date: Sat, 10 Feb 2018 19:09:06 +0800 Message-ID: <20180210110907.5504-3-jeffy.chen@rock-chips.com> References: <20180210110907.5504-1-jeffy.chen@rock-chips.com> Return-path: In-Reply-To: <20180210110907.5504-1-jeffy.chen@rock-chips.com> Sender: linux-kernel-owner@vger.kernel.org To: linux-kernel@vger.kernel.org Cc: briannorris@google.com, dtor@google.com, dianders@google.com, Jeffy Chen , devicetree@vger.kernel.org, Rob Herring , Dmitry Torokhov , linux-input@vger.kernel.org, Mark Rutland List-Id: devicetree@vger.kernel.org Allow specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. Signed-off-by: Jeffy Chen --- Changes in v2: Specify wakeup event action instead of irq trigger type as Brian suggested. Documentation/devicetree/bindings/input/gpio-keys.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/input/gpio-keys.txt b/Documentation/devicetree/bindings/input/gpio-keys.txt index a94940481e55..996ce84352cb 100644 --- a/Documentation/devicetree/bindings/input/gpio-keys.txt +++ b/Documentation/devicetree/bindings/input/gpio-keys.txt @@ -26,6 +26,14 @@ Optional subnode-properties: If not specified defaults to 5. - wakeup-source: Boolean, button can wake-up the system. (Legacy property supported: "gpio-key,wakeup") + - wakeup-event-action: Specifies whether the key should wake the + system when asserted, when deasserted, or both. This property is + only valid for keys that wake up the system (e.g., when the + "wakeup-source" property is also provided). + Supported values are defined in linux-event-codes.h: + EV_ACT_ASSERTED - asserted + EV_ACT_DEASSERTED - deasserted + EV_ACT_ANY - both asserted and deasserted - linux,can-disable: Boolean, indicates that button is connected to dedicated (not shared) interrupt which can be disabled to suppress events from the button. -- 2.11.0