aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBenjamin Tissoires <benjamin.tissoires@redhat.com>2017-03-01 03:57:00 -0500
committerLinus Torvalds <torvalds@linux-foundation.org>2017-03-01 13:01:56 -0500
commit522214d9be9c9f00f34ed89cb95e901b7ac31c59 (patch)
tree7329ec47b24cec04055addd9a05f5ea7b323f495
parent044d5dfd6262d0ef91f6f5b19e3973f82fc7e1d2 (diff)
Input: rmi4 - f30: detect INPUT_PROP_BUTTONPAD from the button count
INPUT_PROP_BUTTONPAD is currently only set through the platform data. The RMI4 header doc says that this property is there to force the buttonpad property, so we also need to detect it by looking at the exported buttons count. Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Reported-and-tested-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--drivers/input/rmi4/rmi_f30.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/drivers/input/rmi4/rmi_f30.c b/drivers/input/rmi4/rmi_f30.c
index 3422464af229..198678613382 100644
--- a/drivers/input/rmi4/rmi_f30.c
+++ b/drivers/input/rmi4/rmi_f30.c
@@ -258,9 +258,10 @@ static int rmi_f30_map_gpios(struct rmi_function *fn,
258 258
259 /* 259 /*
260 * Buttonpad could be also inferred from f30->has_mech_mouse_btns, 260 * Buttonpad could be also inferred from f30->has_mech_mouse_btns,
261 * but I am not sure, so use only the pdata info. 261 * but I am not sure, so use only the pdata info and the number of
262 * mapped buttons.
262 */ 263 */
263 if (pdata->f30_data.buttonpad) 264 if (pdata->f30_data.buttonpad || (button - BTN_LEFT == 1))
264 __set_bit(INPUT_PROP_BUTTONPAD, input->propbit); 265 __set_bit(INPUT_PROP_BUTTONPAD, input->propbit);
265 266
266 return 0; 267 return 0;