On Mon, Sep 17, 2018 at 11:07 AM Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote: > > On Sun, Sep 16, 2018 at 05:54:33PM -0500, Rob Herring wrote: > > On Wed, Sep 05, 2018 at 05:26:47PM +0800, Anson Huang wrote: > > > Add support for wakeup event action, this would allow the device > > > to configure whether to be a wakeup source of system suspend. > > > > > > Signed-off-by: Anson Huang <Anson.Huang@xxxxxxx> > > > --- > > > Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt b/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt > > > index 92fb262..296a9cd 100644 > > > --- a/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt > > > +++ b/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt > > > @@ -6,6 +6,7 @@ Required properties: > > > - interrupts: touch controller interrupt > > > - wakeup-gpios: the gpio pin to be used for waking up the controller > > > and also used as irq pin > > > > If the wakeup gpio is the same as the irq, then this should be removed > > since wakeup-source replaces it. > > No, it does not: it is GPIO that we need to toggle to wake up the > controller, not host, and we do not have generic API to map from IRQ to > GPIO. Ah, okay. > This is also existing binding... Right, I meant removed as in moved to deprecated. Sometimes we just remove the documentation when deprecating. Rob