linux-toradex.git/drivers/input/touchscreen/bu21013_ts.c, branch v5.10-rc4

Input: bu21013_ts - switch to using standard touchscreen properties

2019-09-02T16:07:38+00:00

This switches the driver over to the standard touchscreen properties for
coordinate transformation, while keeping old bindings working as well.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - switch to using MT-B (slotted) protocol

2019-09-02T16:07:38+00:00

MT-B protocol is more efficient and everyone expects it. We use in-kernel
tracking to identify contacts.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - fix suspend when wake source

2019-09-02T16:07:37+00:00

If the touchscreen is configured as wakeup source we should not be cutting
off power to it.

Also, now that the driver relies on I2C client to supply IRQ, we do not
need to explicitly enable and disable IRQ for wakeup: if device is created
as wakeup source, I2C core will mark interrupt as wakeup one.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - use interrupt from I2C client

2019-09-02T16:07:18+00:00

Instead of trying to map INT GPIO to interrupt, let's use one supplied by
I2C client. If there is none - bail. This will also allow us to treat INT
GPIO as optional, as per the binding.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - remove support for platform data

2019-09-02T16:07:17+00:00

There are no current users of the platform data in the tree, and
any new users should either use device tree, or static device
properties to describe the device.

This change drop the platform data definition and handling and moves the
driver over to generic device properties API. We also drop support for the
external clock. If it is needed we will have to extend the bindings to
supply the clock reference and handle it properly in the driver.

Also, wakeup setting should be coming from I2C client.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - convert to using managed resources

2019-09-02T16:07:17+00:00

This allows trimming error unwinding and device removal handling.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - remove useless comments

2019-09-02T16:07:16+00:00

The comments for individual functions in the driver do not provide any
additional information beyond what function names indicate.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - annotate supend/resume methods as __maybe_unused

2019-09-02T16:06:53+00:00

Instead if #ifdef-ing out suspend and resume methods, let's mark
them as __maybe_unused to get better compile time coverage.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - rename some variables

2019-09-02T16:06:52+00:00

"bu21013_data" and "struct bu21013_ts_data" are a tad long, let's call them
"ts" and "struct bu21013_ts".

Also rename retval to error in bu21013_init_chip() and adjust formatting;
i2c_smbus_write_byte_data() returns negative on error and 0 on success, so
we simply test if whether erro is 0 or not.

Tested-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov

Input: bu21013_ts - convert to use GPIO descriptors

2019-09-02T16:06:52+00:00

This driver can use GPIO descriptors rather than GPIO numbers
without any problems, convert it. Name the field variables after
the actual pins on the chip rather than the "reset" and "touch"
names from the devicetree bindings that are vaguely inaccurate.

No in-tree users pass GPIO numbers in platform data so drop
this. Descriptor tables can be used to get these GPIOs from a board
file if need be.

Signed-off-by: Linus Walleij 
Signed-off-by: Dmitry Torokhov