On Tue, Sep 17, 2019 at 05:58:04PM +0200, Marco Felsch wrote: > The default driver behaviour is to enable the wakeup-source everytime. > There are hardware designs which have a dedicated gpio to act as wakeup > device. So it must be allowed to disable the wakeup-source capability. > > This patch adds the binding documentation to disable the wakeup-source > capability. > > Signed-off-by: Marco Felsch <m.felsch@xxxxxxxxxxxxxx> > --- > .../devicetree/bindings/input/touchscreen/edt-ft5x06.txt | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt b/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt > index 870b8c5cce9b..4d6524fe3cf4 100644 > --- a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt > +++ b/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt > @@ -35,6 +35,10 @@ Optional properties: > - pinctrl-0: a phandle pointing to the pin settings for the > control gpios > > + - edt,disable-wakeup-source: If left the device will act as wakeup-source > + (for legacy compatibility). Add the property > + so the device won't act as wakeup-source. I think this is too ugly and I consider it being a bug in the driver that it enables wakeup unconditionally. Let's just update DTS in tree for devices that actually want it (I am curious how many that do not declare "wakeup-source" have it working and actually want it) and key the dirver behavior off the standard property. Until we start seeing this controller in devices that actually have DTS in hardware device tree I think it is better to use standard property. Thanks. -- Dmitry
