[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdYSJ4E1cQk0PPj=D2DMs1d+5J9oFAAi=kmZvF72t1RH6g@mail.gmail.com>
Date: Wed, 8 Jun 2016 09:39:14 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Andrew Duggan <aduggan@...aptics.com>
Cc: Linux Input <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Jiri Kosina <jikos@...nel.org>,
Benjamin Tissoires <benjamin.tissoires@...hat.com>,
Vincent Huang <vincent.huang@...synaptics.com>,
Nick Dyer <nick.dyer@...ev.co.uk>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 3/7] Input: synaptics-rmi4: Add dribble and palm gesture
parameters to devicetree
On Fri, Jun 3, 2016 at 8:40 PM, Andrew Duggan <aduggan@...aptics.com> wrote:
> Signed-off-by: Andrew Duggan <aduggan@...aptics.com>
> +- syna,dribble: Control reporting of dribble packets. Values are 0 for
> + default, 1 for explicitly disable, 2 for explicitly enable.
> +- syna,palm_detect: Control reporting of the palm detect gesture. Values
> + are 0 for default, 1 for explicitly disable, 2 for
> + explicitly enable.
I think these belong in the device tree, but you should add four bool
props instead:
syna,dribble-disable;
syna,dribble-enable;
syna,palm-detect-disable;
syna,palm-detect-enable;
Those are way easier for the human authoring the device tree to
cope with than the opaque parameters.
Yours,
Linus Walleij
Powered by blists - more mailing lists