kernel/drivers/input/touchscreen/ili210x.c, branch linux-5.1.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y2019-02-09T17:01:13ZInput: ili210x - fetch touchscreen geometry from DT2019-02-09T17:01:13ZMarek Vasutmarex@denx.de2019-02-09T16:49:38Zurn:sha1:f67cc3e927d8414ad3872e046764534ea1f5db0d
Fetching the geometry from the ILI251x registers seems unreliable and
sometimes returns all zeroes. Add support for fetching the geometry and
axis inversion from DT instead.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>Input: ili210x - switch to using devm_device_add_group()2019-02-08T07:40:53ZDmitry Torokhovdmitry.torokhov@gmail.com2019-02-07T06:19:42Zurn:sha1:576057bf75cb3e40ff81bb01f021d76b764fdc92
By switching to devm_device_add_group() we can complete driver conversion
to using managed resources and get rid of ili210x_i2c_remove().
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - add ILI251X support2019-02-07T06:18:16ZMarek Vasutmarex@denx.de2019-02-07T06:02:02Zurn:sha1:4958891764749304ac1511f6140ae3888c088e23
Add support for ILI251x touch controller. This controller is similar
to the ILI210x, except for the following differences:
- Does not support I2C R-W transfer, Read must be followed by an
obscenely long delay, and then followed by Write
- Does support 10 simultaneous touch inputs.
- Touch data format is slightly different, pressure reporting does not
work although the touch data contain such information.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - add OF match table2019-02-07T06:18:15ZMarek Vasutmarex@denx.de2019-02-07T06:01:51Zurn:sha1:c5d0e4b5154ac81cffdf6472d5f5e1408faa8ccd
Add OF match table for the ili210x touchscreen.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - reorder probe2019-02-07T06:18:13ZMarek Vasutmarex@denx.de2019-02-07T06:01:30Zurn:sha1:122945776271efee91012c2a345b720d39b15b7c
Perform the register access only after the I2C client data are set,
this is only done in preparation for the subsequent patch which
uses the I2C client data in the register IO function.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - rework the touchscreen sample processing2019-02-07T06:18:12ZMarek Vasutmarex@denx.de2019-02-07T06:01:07Zurn:sha1:e3559442afd2a3d9b09eedc236f19698c515472e
Get rid of the packed structures for representing data as that does not
apply to other similar Ilitek touchscreens. Instead, implement a function
which parses the data and reports touch events and coordinates.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - convert to devm IRQ2019-02-07T06:18:11ZMarek Vasutmarex@denx.de2019-02-07T06:00:44Zurn:sha1:1bdec5d9818c47e080c19784dfd25d1d9c20807e
Convert the driver to devm_request_irq(), drop the related unmanaged
deregistration code and add ili210x_irq_teardown() to tear the IRQ
down and cancel possible touchscreen pending work.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - add reset GPIO support2019-02-07T06:17:46ZMarek Vasutmarex@denx.de2019-02-07T05:55:26Zurn:sha1:201f3c803544c052aa1bab9e562e0ada4aefe03d
The touchscreen can have a reset GPIO connected to it, add support
for such an arrangement.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - convert to devm_ functions2019-02-07T06:17:44ZMarek Vasutmarex@denx.de2019-02-07T05:54:59Zurn:sha1:63083fd582b9eb46a67fff6d4077a931d986d066
Convert the driver to dev-managed allocations.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: ili210x - drop get_pendown_state2019-02-07T06:17:43ZMarek Vasutmarex@denx.de2019-02-07T05:54:37Zurn:sha1:2fa928390f3f04fbb29267b29ca09d980b17f9d1
The .get_pendown_state callback is set only by the platform data code,
which was just removed. Thus, get_pendown_state() always returns false,
so drop that altogether.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>