kernel/linux.git/drivers/input/touchscreen/st1232.c, branch v5.10.257

Input: st1232 - switch to using MT-B protocol

2019-10-29T04:04:27+00:00

Switch the driver to the slotted variant of multitouch protocol (MT-B) with in-kernel tracking of the contacts. Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - note that the receive buffer is DMA-safe

2019-10-29T04:04:16+00:00

The receiving buffer is allocated separately from the main driver data structure, and is naturally DMA-safe, so mark it as such when building I2C transfer message. Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - do not set parent device explicitly

2019-10-29T04:03:55+00:00

devm_input_allocate_device() already sets parent device for us. Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - do not allocate fingers data separately

2019-10-29T04:01:58+00:00

The finger structure size is quite small and allocating it together with the main driver structure will not increase likelyhood of allocation failing, but reduces number of objects needing to be tracked by the allocator and devm. Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - do not reset the chip too early

2019-10-29T04:01:46+00:00

We should not be putting the chip into reset while interrupts are enabled and ISR may be running. Fix this by installing a custom devm action and powering off the device/resetting GPIO line from there. This ensures proper ordering. Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - rely on I2C core to configure wakeup interrupt

2019-10-29T04:01:34+00:00

When I2C client is created with I2C_CLIENT_WAKE flag (which happens either because we have "wakeup-source" device property or the flag was passed in when creating an I2C client manually), I2C core will take care of configuring interrupt as wakeup source on suspend. Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - do not unconditionally configure as wakeup source

2019-10-29T04:01:24+00:00

Do not unconditionally configure the touchscreen as wakeup source but rather rely on I2C core to do that when requested (either via "wakeup-source" device property, or when creating a client with I2C_CLIENT_WAKE flag). Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - simplify parsing of read buffer

2019-10-29T04:01:12+00:00

Avoid complex 2-variable loop when parsing touchscreen data to make the code clearer. Acked-by: Martin Kepplinger Tested-by: Matthias Fend Signed-off-by: Dmitry Torokhov

Input: st1232 - fix reporting multitouch coordinates

2019-10-21T17:15:03+00:00

For Sitronix st1633 multi-touch controller driver the coordinates reported for multiple fingers were wrong, as it was always taking LSB of coordinates from the first contact data. Signed-off-by: Dixit Parmar Reviewed-by: Martin Kepplinger Cc: stable@vger.kernel.org Fixes: 351e0592bfea ("Input: st1232 - add support for st1633") Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204561 Link: https://lore.kernel.org/r/1566209314-21767-1-git-send-email-dixitparmar19@gmail.com Signed-off-by: Dmitry Torokhov

Input: st1232 - handle common DT bindings

2019-02-17T05:39:42+00:00

This is required to specify generic touchscreen properties via DT. Signed-off-by: Matthias Fend Reviewed-by: Rob Herring Signed-off-by: Dmitry Torokhov