[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180310181159.GA260013@dtor-ws>
Date: Sat, 10 Mar 2018 10:11:59 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Jeffy Chen <jeffy.chen@...k-chips.com>,
linux-kernel@...r.kernel.org, briannorris@...gle.com,
heiko@...ech.de, dtor@...gle.com, dianders@...gle.com,
devicetree@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
Thomas Gleixner <tglx@...utronix.de>,
Joseph Lo <josephl@...dia.com>,
stephen lu <lumotuwe@...il.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
linux-input@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mark Rutland <mark.rutland@....com>,
Philippe Ombredanne <pombredanne@...b.com>,
Arvind Yadav <arvind.yadav.cs@...il.com>
Subject: Re: [PATCH v5 1/3] Input: gpio-keys - add support for wakeup event
action
On Fri, Mar 09, 2018 at 05:27:21PM -0600, Rob Herring wrote:
> On Thu, Mar 08, 2018 at 03:32:11PM +0800, Jeffy Chen wrote:
> > Add support for specifying event actions to trigger wakeup when using
> > the gpio-keys input device as a wakeup source.
> >
> > This would allow the device to configure when to wakeup the system. For
> > example a gpio-keys input device for pen insert, may only want to wakeup
> > the system when ejecting the pen.
> >
> > Suggested-by: Brian Norris <briannorris@...omium.org>
> > Signed-off-by: Jeffy Chen <jeffy.chen@...k-chips.com>
> > ---
> >
> > Changes in v5:
> > Remove unneeded irq_wake flag as Andy suggested.
> >
> > Changes in v4:
> > Add dt-binding gpio-keys.h, stop saving irq trigger type, add enable/disable wakeup helpers as Dmitry suggested.
> >
> > Changes in v3:
> > Adding more comments as Brian suggested.
> >
> > Changes in v2:
> > Specify wakeup event action instead of irq trigger type as Brian
> > suggested.
> >
> > drivers/input/keyboard/gpio_keys.c | 63 +++++++++++++++++++++++++++++++++--
> > include/dt-bindings/input/gpio-keys.h | 13 ++++++++
>
> This file should be in the binding patch.
No, this is a folly. Both the header, along with the documentation (i.e.
binding doc) should be together with the patch that introduces the
changes. The patches are supposed to be self contained and sufficient to
stand on their own. Neither this header, not the binding doc make
sense without the change to the driver itself.
Next we'll start adding #defines in a separate patch before using
them...
Thanks.
--
Dmitry
Powered by blists - more mailing lists