kernel/linux.git/drivers/input/touchscreen/zforce_ts.c, branch v3.18.94

Input: zforce_ts - fix dual touch recognition

2016-07-12T12:48:03+00:00

[ Upstream commit 6984ab1ab35f422292b7781c65284038bcc0f6a6 ] A wrong decoding of the touch coordinate message causes a wrong touch ID. Touch ID for dual touch must be 0 or 1. According to the actual Neonode nine byte touch coordinate coding, the state is transported in the lower nibble and the touch ID in the higher nibble of payload byte five. Signed-off-by: Knut Wohlrab Signed-off-by: Oleksij Rempel Signed-off-by: Dirk Behme Signed-off-by: Dmitry Torokhov Signed-off-by: Sasha Levin

Input: zforce - add regulator handling

2014-07-21T17:28:53+00:00

It's possible that the controller has an individually switchable power supply. Therefore add support to control a supplying regulator. As this is not always the case, the regulator is requested as optional. Signed-off-by: Heiko Stuebner Signed-off-by: Dmitry Torokhov

Input: zforce - make of_device_id array const

2014-05-14T23:40:01+00:00

Make of_device_id array const, because all OF functions handle it as const. Signed-off-by: Jingoo Han Acked-by: Heiko Stuebner Signed-off-by: Dmitry Torokhov

Merge tag 'v3.14-rc4' into next

2014-03-01T18:31:53+00:00

Merge with Linux 3.14-rc4 to bring devm_request_any_context_irq().

Input: zforce - add devicetree support

2014-01-28T06:35:42+00:00

This makes the zforce driver usable on devicetree-based platforms too. Signed-off-by: Heiko Stuebner Signed-off-by: Dmitry Torokhov

Input: zforce - use internal pdata pointer instead of dev_get_platdata

2014-01-28T06:35:18+00:00

Devicetree support will be creating its own platfprm data structure that is not attached to the device. Let's use the internal pointer to the pdata instead of re-fetching it with dev_get_platdata(). Signed-off-by: Heiko Stuebner Signed-off-by: Dmitry Torokhov

Input: zforce - reduce stack memory allocated to frames

2014-01-28T06:35:17+00:00

A frame is a u8 array with the following structure: [PAYLOAD_HEADER, PAYLOAD_LENGTH, ...PAYLOAD_BODY...] PAYLOAD_BODY can be at most 255 bytes long, as it's size is represented by PAYLOAD_LENGTH. Therefore we can reduce the stack memory allocated to payload_buffer[] roughly by half, from 512 to 257 bytes. Signed-off-by: Luis Ortega Acked-by: Heiko Stuebner Tested-by: Heiko Stuebner - bq Cervantes (imx6sl) Signed-off-by: Dmitry Torokhov

Input: zforce - remove unnecessary payload data checks

2014-01-28T06:35:17+00:00

The function zforce_read_packet() reads 2 values (bytes) of payload header, validates them and then proceeds to read the payload body. The function stores all these in a u8 buffer. The PAYLOAD_LENGTH check seems to be trying to detect an overflow error. However, since we are just reading a u8 value from the buffer, these checks are unnecessary and we should simply compare against zero. Signed-off-by: Luis Ortega Acked-by: Heiko Stuebner Tested-by: Heiko Stuebner - bq Cervantes (imx6sl) Signed-off-by: Dmitry Torokhov

Input: zforce - fix lines exceeding 80 columns

2014-01-28T06:35:16+00:00

Fixed lines exceeding 80 characters long wherever possible, as per the coding style. Signed-off-by: Luis Ortega Acked-by: Heiko Stuebner Signed-off-by: Dmitry Torokhov

Input: zforce - fix spelling errors

2014-01-28T06:35:00+00:00

Fixed a few spelling errors. Signed-off-by: Luis Ortega Acked-by: Heiko Stuebner Signed-off-by: Dmitry Torokhov