From: Daniel Kurtz Date: Thu, 28 Jun 2012 13:08:06 +0000 (+0800) Subject: Input: atmel_mxt_ts - don't read T5 when dumping objects X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=55d6867fe659f4783e57db7b2ae0bb04e4ac816e;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git Input: atmel_mxt_ts - don't read T5 when dumping objects T5 is the message processor object. Reading it will only have two outcomes, neither of which is particularly useful: 1) the message count decrements, and a valid message will be lost 2) an invalid message will be read (reportid == 0xff) Signed-off-by: Daniel Kurtz Signed-off-by: Henrik Rydberg --- diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c index c72f595a3203..9f8dd973e5f5 100644 --- a/drivers/input/touchscreen/atmel_mxt_ts.c +++ b/drivers/input/touchscreen/atmel_mxt_ts.c @@ -263,7 +263,6 @@ struct mxt_data { static bool mxt_object_readable(unsigned int type) { switch (type) { - case MXT_GEN_MESSAGE_T5: case MXT_GEN_COMMAND_T6: case MXT_GEN_POWER_T7: case MXT_GEN_ACQUIRE_T8: