input: elants: Support Asus TF300T touchscreen
Subsystems (3)
v3 cover input: elants: Support Asus TF300T touchscreen
This series cleans up the driver a bit and implements changes needed to support EKTF3624-based touchscreen used in Asus TF300T and similar Tegra3-based tablets.
---
v2: extended with Dmitry's patches (replaced v1 patches 3 and 4)
v3: rebased for v5.7-rc1
Dmitry Osipenko (3):
input: elants: support 0x66 reply opcode for reporting touches
dt-bindings: input: elants-i2c: Document common touchscreen properties
dt-bindings: input: elants-i2c: Document eKTF3624
Michał Mirosław (6):
input: elants: document some registers and values
input: elants: support old touch report format
input: elants: remove unused axes
input: elants: override touchscreen info with DT properties
input: elants: refactor elants_i2c_execute_command()
input: elants: read touchscreen size for EKTF3624
.../devicetree/bindings/input/elants_i2c.txt | 6 +- drivers/input/touchscreen/elants_i2c.c | 365 ++++++++++++------ 2 files changed, 242 insertions(+), 129 deletions(-)
Signature · 1 line
2.20.1
PATCH v3 1/9 input: elants: document some registers and values
Add information found in downstream kernels, to make the code less magic.
--- drivers/input/touchscreen/elants_i2c.c | 29 +++++++++++++++++++++----- 1 file changed, 24 insertions(+), 5 deletions(-)
drivers/input/touchscreen/elants_i2c.c +24 -5
@@ -79,7 +79,11 @@#define HEADER_REPORT_10_FINGER 0x62 -/* Header (4 bytes) plus 3 fill 10-finger packets */ +/* Power state */ +#define PWR_STATE_DEEP_SLEEP 0 +#define PWR_STATE_NORMAL 1 + +/* Header (4 bytes) plus 3 full 10-finger packets */ #define MAX_PACKET_SIZE 169#define BOOT_TIME_DELAY_MS 50
@@ -89,10 +93,21 @@#define E_ELAN_INFO_BC_VER 0x10#define E_ELAN_INFO_TEST_VER 0xE0#define E_ELAN_INFO_FW_ID 0xF0 +#define E_POWER_MODE 0x40 +#define E_POWER_STATE 0x50 +#define E_INFO_X_RES 0x60 +#define E_INFO_Y_RES 0x63#define E_INFO_OSR 0xD6#define E_INFO_PHY_SCAN 0xD7#define E_INFO_PHY_DRIVER 0xD8 +/* FW write command, 0x54 0x?? 0x0, 0x01 */ +#define E_POWER_MODE_BATTERY 0x40 +#define E_POWER_MODE_AC 0x41 +#define E_POWER_MODE_USB 0x42 +#define E_POWER_STATE_SLEEP 0x50 +#define E_POWER_STATE_RESUME 0x58 +#define MAX_RETRIES 3#define MAX_FW_UPDATE_RETRIES 30
@@ -237,8 +252,8 @@ static int elants_i2c_calibrate(struct elants_data *ts) {struct i2c_client *client = ts->client;int ret, error; -static const u8 w_flashkey[] = {0x54 ,0xC0 ,0xE1 ,0x5A }; -static const u8 rek[] = {0x54 ,0x29 ,0x00 ,0x01 }; +static const u8 w_flashkey[] = {CMD_HEADER_WRITE ,0xC0 ,0xE1 ,0x5A }; +static const u8 rek[] = {CMD_HEADER_WRITE ,0x29 ,0x00 ,0x01 };static const u8 rek_resp[] = {CMD_HEADER_REK ,0x66 ,0x66 ,0x66 };disable_irq (client->irq);
@@ -1357,7 +1372,9 @@ static int __maybe_unused elants_i2c_suspend(struct device *dev) {struct i2c_client *client =to_i2c_client (dev);struct elants_data *ts =i2c_get_clientdata (client); -const u8 set_sleep_cmd[] = {0x54 ,0x50 ,0x00 ,0x01 }; +const u8 set_sleep_cmd[] = { +CMD_HEADER_WRITE ,E_POWER_STATE_SLEEP ,0x00 ,0x01 + };int retry_cnt;int error;
@@ -1394,7 +1411,9 @@ static int __maybe_unused elants_i2c_resume(struct device *dev) {struct i2c_client *client =to_i2c_client (dev);struct elants_data *ts =i2c_get_clientdata (client); -const u8 set_active_cmd[] = {0x54 ,0x58 ,0x00 ,0x01 }; +const u8 set_active_cmd[] = { +CMD_HEADER_WRITE ,E_POWER_STATE_RESUME ,0x00 ,0x01 + };int retry_cnt;int error;
Signature · 1 line
2.20.1
PATCH v3 2/9 input: elants: support old touch report format
In reply to Michał MirosławSupport ELAN touchpad sensor with older firmware as found on eg. Asus Transformer Pads.
--- drivers/input/touchscreen/elants_i2c.c | 36 ++++++++++++++++++-------- 1 file changed, 25 insertions(+), 11 deletions(-)
drivers/input/touchscreen/elants_i2c.c +25 -11
@@ -67,6 +67,7 @@#define CMD_HEADER_REK 0x66/* FW position data */ +#define PACKET_SIZE_OLD 40#define PACKET_SIZE 55#define MAX_CONTACT_NUM 10#define FW_POS_HEADER 0
@@ -853,7 +854,8 @@ static int elants_i2c_fw_update(struct elants_data *ts)* Event reporting. */ -static void elants_i2c_mt_event (struct elants_data *ts,u8 *buf) +static void elants_i2c_mt_event (struct elants_data *ts,u8 *buf, +size_t report_len) {struct input_dev *input = ts->input;unsigned int n_fingers;
@@ -865,7 +867,8 @@ static void elants_i2c_mt_event(struct elants_data *ts, u8 *buf) buf[FW_POS_STATE ];dev_dbg (&ts->client->dev, -"n_fingers: %u, state: %04x\n" , n_fingers, finger_state); +"n_fingers: %u, state: %04x, report_len: %zu\n" , + n_fingers, finger_state, report_len);for (i =0 ; i <MAX_CONTACT_NUM && n_fingers; i++) {if (finger_state &1 ) {
@@ -875,8 +878,16 @@ static void elants_i2c_mt_event(struct elants_data *ts, u8 *buf) pos = &buf[FW_POS_XY + i *3 ]; x = (((u16 )pos[0 ] &0xf0 ) <<4 ) | pos[1 ]; y = (((u16 )pos[0 ] &0x0f ) <<8 ) | pos[2 ]; - p = buf[FW_POS_PRESSURE + i]; - w = buf[FW_POS_WIDTH + i]; +if (report_len ==PACKET_SIZE_OLD ) { + w = buf[FW_POS_WIDTH + i /2 ]; + w >>=4 * (~i &1 );// little-endian-nibbles + w |= w <<4 ; + w |= !w; + p = w; + }else { + p = buf[FW_POS_PRESSURE + i]; + w = buf[FW_POS_WIDTH + i]; + }dev_dbg (&ts->client->dev,"i=%d x=%d y=%d p=%d w=%d\n" , i, x, y, p, w);
@@ -909,7 +920,8 @@ static u8 elants_i2c_calculate_checksum(u8 *buf)return checksum; } -static void elants_i2c_event (struct elants_data *ts,u8 *buf) +static void elants_i2c_event (struct elants_data *ts,u8 *buf, +size_t report_len) {u8 checksum =elants_i2c_calculate_checksum (buf);
@@ -923,7 +935,7 @@ static void elants_i2c_event(struct elants_data *ts, u8 *buf)"%s: unknown packet type: %02x\n" , __func__, buf[FW_POS_HEADER]); else -elants_i2c_mt_event (ts ,buf ); +elants_i2c_mt_event (ts ,buf ,report_len ); }static irqreturn_t elants_i2c_irq (int irq,void *_dev)
@@ -981,7 +993,8 @@ static irqreturn_t elants_i2c_irq(int irq, void *_dev)break ;case QUEUE_HEADER_SINGLE : -elants_i2c_event (ts, &ts->buf[HEADER_SIZE ]); +elants_i2c_event (ts, &ts->buf[HEADER_SIZE ], + ts->buf[FW_HDR_LENGTH ]);break ;case QUEUE_HEADER_NORMAL :
@@ -994,17 +1007,18 @@ static irqreturn_t elants_i2c_irq(int irq, void *_dev) } report_len = ts->buf[FW_HDR_LENGTH ] / report_count; -if (report_len !=PACKET_SIZE ) { +if (report_len !=PACKET_SIZE && + report_len !=PACKET_SIZE_OLD ) {dev_err (&client->dev, -"mismatching report length: %*ph\n" , +"unsupported report length: %*ph\n" ,HEADER_SIZE , ts->buf);break ; }for (i =0 ; i < report_count; i++) {u8 *buf = ts->buf +HEADER_SIZE + - i *PACKET_SIZE ; -elants_i2c_event (ts, buf); + i * report_len; +elants_i2c_event (ts, buf, report_len); }break ;
Signature · 1 line
2.20.1
PATCH v3 3/9 input: elants: remove unused axes
In reply to Michał MirosławDriver only ever reports MT events. Clear capabilities of all others.
--- drivers/input/touchscreen/elants_i2c.c | 11 ----------- 1 file changed, 11 deletions(-)
drivers/input/touchscreen/elants_i2c.c +0 -11
@@ -1312,17 +1312,6 @@ static int elants_i2c_probe(struct i2c_client *client, ts->input->name ="Elan Touchscreen" ; ts->input->id.bustype =BUS_I2C ; -__set_bit (BTN_TOUCH , ts->input->keybit); -__set_bit (EV_ABS , ts->input->evbit); -__set_bit (EV_KEY , ts->input->evbit); - -/* Single touch input params setup */ -input_set_abs_params (ts->input,ABS_X ,0 , ts->x_max,0 ,0 ); -input_set_abs_params (ts->input,ABS_Y ,0 , ts->y_max,0 ,0 ); -input_set_abs_params (ts->input,ABS_PRESSURE ,0 ,255 ,0 ,0 ); -input_abs_set_res (ts->input,ABS_X , ts->x_res); -input_abs_set_res (ts->input,ABS_Y , ts->y_res); -/* Multitouch input params setup */ error =input_mt_init_slots (ts->input,MAX_CONTACT_NUM ,INPUT_MT_DIRECT |INPUT_MT_DROP_UNUSED );
Signature · 1 line
2.20.1
Dmitry Torokhov
maintainerRe: [PATCH v3 3/9] input: elants: remove unused axes
Quoted 1 line · Michał Mirosław
Driver only ever reports MT events. Clear capabilities of all others.
This is not true. input_mt_sync_frame() calls input_mt_report_pointer_emulation() which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).
Thanks.
Signature · 1 line
Dmitry
Re: [PATCH v3 3/9] input: elants: remove unused axes
26.04.2020 07:52, Dmitry Torokhov пишет:
Quoted 7 lines · Michał Mirosław
Quoted 1 line
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).
That's a good catch, thank you very much for the clarification!
Re: [PATCH v3 3/9] input: elants: remove unused axes
In reply to Dmitry TorokhovQuoted 6 lines · Dmitry Torokhov
Quoted 1 line · Michał Mirosław
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).
Oh, I didn't notice that. Looking at the code, I see that input_mt_init_slots() sets up the emulated axes in this case.
Do you need me to update the commitmsg?
Best Regards,
Michał Mirosław
Re: [PATCH v3 3/9] input: elants: remove unused axes
26.04.2020 14:21, Michał Mirosław пишет:
Quoted 8 lines · Dmitry Torokhov
Quoted 6 lines · Michał Mirosław
Quoted 1 line
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).
Quoted 4 lines
Oh, I didn't notice that. Looking at the code, I see that
input_mt_init_slots()sets up the emulated axes in this case.Do you need me to update the commitmsg?
I tried Ubuntu 12.04 that uses ancient libinput (or whatever it was back then), which doesn't support MT. Mouse doesn't move at all with this patch being applied. Without this patch mouse moves, but it's not usable because the cursor's position is wrong, i.e. mouse position doesn't match the screen touches.
This means that input_mt_report_pointer_emulation() doesn't set up everything needed for the legacy pointer emulation.
Re: [PATCH v3 3/9] input: elants: remove unused axes
26.04.2020 18:39, Dmitry Osipenko пишет:
Quoted 14 lines
26.04.2020 14:21, Michał Mirosław пишет:
Quoted 8 lines · Dmitry Torokhov
Quoted 6 lines · Michał Mirosław
Quoted 1 line
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).Quoted 4 lines
Oh, I didn't notice that. Looking at the code, I see that
input_mt_init_slots()sets up the emulated axes in this case.Do you need me to update the commitmsg?
Quoted 9 lines
I tried Ubuntu 12.04 that uses ancient libinput (or whatever it was back then), which doesn't support MT. Mouse doesn't move at all with this patch being applied. Without this patch mouse moves, but it's not usable because the cursor's position is wrong, i.e. mouse position doesn't match the screen touches.
This means that
input_mt_report_pointer_emulation()doesn't set up everything needed for the legacy pointer emulation.
I meant the input_mt_init_slots().
Re: [PATCH v3 3/9] input: elants: remove unused axes
26.04.2020 18:41, Dmitry Osipenko пишет:
Quoted 13 lines
26.04.2020 18:39, Dmitry Osipenko пишет:
Quoted 12 lines
26.04.2020 14:21, Michał Mirosław пишет:
Quoted 11 lines · Dmitry Torokhov
Quoted 6 lines · Michał Mirosław
Quoted 1 line
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).Oh, I didn't notice that. Looking at the code, I see that
input_mt_init_slots()sets up the emulated axes in this case.
Quoted 9 lines
Quoted 5 lines
Quoted 1 line
Do you need me to update the commitmsg?
I tried Ubuntu 12.04 that uses ancient libinput (or whatever it was back then), which doesn't support MT. Mouse doesn't move at all with this patch being applied.
Without this patch mouse moves, but it's not usable
Quoted 2 lines
because the cursor's position is wrong, i.e. mouse position doesn't match the screen touches.
The fix for the legacy pointer emulation is trivial:
--- >8 ---
(quoted diff) +0 -0
b/drivers/input/touchscreen/elants_i2c.c
index 060c60c04f25..3644b5b48081 100644
drivers/input/touchscreen/elants_i2c.c +2 -0
@@ -1414,6 +1414,8 @@ static int elants_i2c_probe(struct i2c_client *client,input_abs_set_res (ts->input,ABS_X , ts->x_res);input_abs_set_res (ts->input,ABS_Y , ts->y_res); +touchscreen_parse_properties (ts->input, false, &ts->prop); +/* Multitouch input params setup */ error =input_mt_init_slots (ts->input,MAX_CONTACT_NUM ,INPUT_MT_DIRECT |INPUT_MT_DROP_UNUSED );
--- >8 ---
Michał, please incorporate this change into the next version.
Quoted 6 lines
Quoted 3 lines
This means that
input_mt_report_pointer_emulation()doesn't set up everything needed for the legacy pointer emulation.I meant the
input_mt_init_slots().
Re: [PATCH v3 3/9] input: elants: remove unused axes
In reply to Dmitry OsipenkoQuoted 21 lines · Dmitry Osipenko
26.04.2020 18:39, Dmitry Osipenko пишет:
Quoted 20 lines
26.04.2020 14:21, Michał Mirosław пишет:
Quoted 8 lines · Dmitry Torokhov
Quoted 6 lines · Michał Mirosław
Quoted 1 line
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).Quoted 4 lines
Oh, I didn't notice that. Looking at the code, I see that
input_mt_init_slots()sets up the emulated axes in this case.Do you need me to update the commitmsg?
I tried Ubuntu 12.04 that uses ancient libinput (or whatever it was back then), which doesn't support MT. Mouse doesn't move at all with this patch being applied. Without this patch mouse moves, but it's not usable because the cursor's position is wrong, i.e. mouse position doesn't match the screen touches.
Quoted 5 lines
Quoted 3 lines
This means that
input_mt_report_pointer_emulation()doesn't set up everything needed for the legacy pointer emulation.I meant the
input_mt_init_slots().
Can you try v4 and see if it helps? input_mt_init_slots() needs other axes set up before for it to use correct ranges.
Best Regards
Michał Mirosław
Re: [PATCH v3 3/9] input: elants: remove unused axes
26.04.2020 19:12, Michał Mirosław пишет:
Quoted 22 lines · Dmitry Osipenko
Quoted 21 lines
26.04.2020 18:39, Dmitry Osipenko пишет:
Quoted 20 lines
26.04.2020 14:21, Michał Mirosław пишет:
Quoted 8 lines · Dmitry Torokhov
Quoted 6 lines · Michał Mirosław
Quoted 1 line
Driver only ever reports MT events. Clear capabilities of all others.
This is not true.
input_mt_sync_frame()callsinput_mt_report_pointer_emulation()which does emut single-touch events for the benefit of older userspace (or userspace that is not interested in multitouch).Quoted 4 lines
Oh, I didn't notice that. Looking at the code, I see that
input_mt_init_slots()sets up the emulated axes in this case.Do you need me to update the commitmsg?
I tried Ubuntu 12.04 that uses ancient libinput (or whatever it was back then), which doesn't support MT. Mouse doesn't move at all with this patch being applied. Without this patch mouse moves, but it's not usable because the cursor's position is wrong, i.e. mouse position doesn't match the screen touches.
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
This means that
input_mt_report_pointer_emulation()doesn't set up everything needed for the legacy pointer emulation.I meant the
input_mt_init_slots().Can you try v4 and see if it helps?
input_mt_init_slots()needs other axes set up before for it to use correct ranges.
Sure! I'll try it right now.
PATCH v3 4/9 input: elants: override touchscreen info with DT properties
In reply to Michał MirosławAllow overriding of information from hardware and support additional common DT properties like axis inversion. This is required for eg. Nexus 7 and TF300T where the programmed values in firmware differ from reality.
--- drivers/input/touchscreen/elants_i2c.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/input/touchscreen/elants_i2c.c +5 -2
@@ -32,6 +32,7 @@#include <linux/slab.h> #include <linux/firmware.h> #include <linux/input/mt.h> +#include <linux/input/touchscreen.h> #include <linux/acpi.h> #include <linux/of.h> #include <linux/gpio/consumer.h>
@@ -150,6 +151,7 @@ struct elants_data {unsigned int y_res;unsigned int x_max;unsigned int y_max; +struct touchscreen_properties prop;enum elants_state state;enum elants_iap_mode iap_mode;
@@ -894,8 +896,7 @@ static void elants_i2c_mt_event(struct elants_data *ts, u8 *buf,input_mt_slot (input, i);input_mt_report_slot_state (input,MT_TOOL_FINGER , true); -input_event (input,EV_ABS ,ABS_MT_POSITION_X , x); -input_event (input,EV_ABS ,ABS_MT_POSITION_Y , y); +touchscreen_report_pos (input, &ts->prop, x, y, true);input_event (input,EV_ABS ,ABS_MT_PRESSURE , p);input_event (input,EV_ABS ,ABS_MT_TOUCH_MAJOR , w);
@@ -1329,6 +1330,8 @@ static int elants_i2c_probe(struct i2c_client *client,input_abs_set_res (ts->input,ABS_MT_POSITION_Y , ts->y_res);input_abs_set_res (ts->input,ABS_MT_TOUCH_MAJOR ,1 ); +touchscreen_parse_properties (ts->input, true, &ts->prop); + error =input_register_device (ts->input);if (error) { dev_err(&client->dev,
Signature · 1 line
2.20.1
Dmitry Torokhov
maintainerRe: [PATCH v3 4/9] input: elants: override touchscreen info with DT properties
Quoted 8 lines · Michał Mirosław
Allow overriding of information from hardware and support additional common DT properties like axis inversion. This is required for eg. Nexus 7 and TF300T where the programmed values in firmware differ from reality.
Signed-off-by Dmitry Osipenko <[email protected]>[moved "prop" before DMA buffer]Signed-off-by Michał Mirosław <[email protected]>
This needs a companion patch for the DT bindings.
Quoted 46 lines
--- drivers/input/touchscreen/elants_i2c.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)drivers/input/touchscreen/elants_i2c.c +5
-2@@ -32,6 +32,7 @@#include <linux/slab.h> #include <linux/firmware.h> #include <linux/input/mt.h> +#include <linux/input/touchscreen.h> #include <linux/acpi.h> #include <linux/of.h> #include <linux/gpio/consumer.h> @@ -150,6 +151,7 @@ struct elants_data {unsigned int y_res;unsigned int x_max;unsigned int y_max; +struct touchscreen_properties prop;enum elants_state state;enum elants_iap_mode iap_mode;@@ -894,8 +896,7 @@ static void elants_i2c_mt_event(struct elants_data *ts, u8 *buf,input_mt_slot (input, i);input_mt_report_slot_state (input,MT_TOOL_FINGER , true); -input_event (input,EV_ABS ,ABS_MT_POSITION_X , x); -input_event (input,EV_ABS ,ABS_MT_POSITION_Y , y); +touchscreen_report_pos (input, &ts->prop, x, y, true);input_event (input,EV_ABS ,ABS_MT_PRESSURE , p);input_event (input,EV_ABS ,ABS_MT_TOUCH_MAJOR , w);@@ -1329,6 +1330,8 @@ static int elants_i2c_probe(struct i2c_client *client,input_abs_set_res (ts->input,ABS_MT_POSITION_Y , ts->y_res);input_abs_set_res (ts->input,ABS_MT_TOUCH_MAJOR ,1 ); +touchscreen_parse_properties (ts->input, true, &ts->prop); + error =input_register_device (ts->input);if (error) { dev_err(&client->dev,Signature · 1 line
2.20.1
Signature · 1 line
Dmitry
Dmitry Torokhov
maintainerRe: [PATCH v3 4/9] input: elants: override touchscreen info with DT properties
Quoted 11 lines · Dmitry Torokhov
Quoted 8 lines · Michał Mirosław
Allow overriding of information from hardware and support additional common DT properties like axis inversion. This is required for eg. Nexus 7 and TF300T where the programmed values in firmware differ from reality.
Signed-off-by Dmitry Osipenko <[email protected]>[moved "prop" before DMA buffer]Signed-off-by Michał Mirosław <[email protected]>This needs a companion patch for the DT bindings.
Ah, sorry, I missed the fact that it was later in the sequence.
Quoted 50 lines
Quoted 47 lines
--- drivers/input/touchscreen/elants_i2c.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)drivers/input/touchscreen/elants_i2c.c +5
-2@@ -32,6 +32,7 @@#include <linux/slab.h> #include <linux/firmware.h> #include <linux/input/mt.h> +#include <linux/input/touchscreen.h> #include <linux/acpi.h> #include <linux/of.h> #include <linux/gpio/consumer.h> @@ -150,6 +151,7 @@ struct elants_data {unsigned int y_res;unsigned int x_max;unsigned int y_max; +struct touchscreen_properties prop;enum elants_state state;enum elants_iap_mode iap_mode;@@ -894,8 +896,7 @@ static void elants_i2c_mt_event(struct elants_data *ts, u8 *buf,input_mt_slot (input, i);input_mt_report_slot_state (input,MT_TOOL_FINGER , true); -input_event (input,EV_ABS ,ABS_MT_POSITION_X , x); -input_event (input,EV_ABS ,ABS_MT_POSITION_Y , y); +touchscreen_report_pos (input, &ts->prop, x, y, true);input_event (input,EV_ABS ,ABS_MT_PRESSURE , p);input_event (input,EV_ABS ,ABS_MT_TOUCH_MAJOR , w);@@ -1329,6 +1330,8 @@ static int elants_i2c_probe(struct i2c_client *client,input_abs_set_res (ts->input,ABS_MT_POSITION_Y , ts->y_res);input_abs_set_res (ts->input,ABS_MT_TOUCH_MAJOR ,1 ); +touchscreen_parse_properties (ts->input, true, &ts->prop); + error =input_register_device (ts->input);if (error) { dev_err(&client->dev,Signature · 1 line
2.20.1Signature · 1 line
Dmitry
Signature · 1 line
Dmitry
PATCH v3 5/9 input: elants: refactor elants_i2c_execute_command()
In reply to Michał MirosławApply some DRY-ing to elants_i2c_execute_command() callers. This pulls polling and error printk()s into a single function.
--- drivers/input/touchscreen/elants_i2c.c | 189 +++++++++++++------------ 1 file changed, 96 insertions(+), 93 deletions(-)
drivers/input/touchscreen/elants_i2c.c +96 -93
@@ -205,7 +205,8 @@ static int elants_i2c_read(struct i2c_client *client, void *data, size_t size)static int elants_i2c_execute_command (struct i2c_client *client,const u8 *cmd,size_t cmd_size, -u8 *resp,size_t resp_size) +u8 *resp,size_t resp_size, +int retries,const char *cmd_name) {struct i2c_msg msgs[2 ];int ret;
@@ -225,30 +226,55 @@ static int elants_i2c_execute_command(struct i2c_client *client,break ;default : -dev_err (&client->dev,"%s: invalid command %*ph\n" , - __func__, (int )cmd_size, cmd); +dev_err (&client->dev,"(%s): invalid command: %*ph\n" , + cmd_name, (int )cmd_size, cmd);return -EINVAL ; } - msgs[0 ].addr = client->addr; - msgs[0 ].flags = client->flags &I2C_M_TEN ; - msgs[0 ].len = cmd_size; - msgs[0 ].buf = (u8 *)cmd; +for (;;) { + msgs[0 ].addr = client->addr; + msgs[0 ].flags = client->flags &I2C_M_TEN ; + msgs[0 ].len = cmd_size; + msgs[0 ].buf = (u8 *)cmd; - msgs[1 ].addr = client->addr; - msgs[1 ].flags = client->flags &I2C_M_TEN ; - msgs[1 ].flags |=I2C_M_RD ; - msgs[1 ].len = resp_size; - msgs[1 ].buf = resp; + msgs[1 ].addr = client->addr; + msgs[1 ].flags = client->flags &I2C_M_TEN ; + msgs[1 ].flags |=I2C_M_RD ; + msgs[1 ].len = resp_size; + msgs[1 ].buf = resp; - ret =i2c_transfer (client->adapter, msgs,ARRAY_SIZE (msgs)); -if (ret <0 ) -return ret; + ret =i2c_transfer (client->adapter, msgs,ARRAY_SIZE (msgs)); +if (ret <0 ) { +if (--retries >0 ) { +dev_dbg (&client->dev, +"(%s) I2C transfer failed: %d (retrying)\n" , + cmd_name, ret); +continue ; + } -if (ret !=ARRAY_SIZE (msgs) || resp[FW_HDR_TYPE ] != expected_response) -return -EIO ; +dev_err (&client->dev, +"(%s) I2C transfer failed: %d\n" , + cmd_name, ret); +return ret; + } -return 0 ; +if (ret !=ARRAY_SIZE (msgs) || + resp[FW_HDR_TYPE ] != expected_response) { +if (--retries >0 ) { +dev_dbg (&client->dev, +"(%s) unexpected response: %*ph (retrying)\n" , + cmd_name, ret, resp); +continue ; + } + +dev_err (&client->dev, +"(%s) unexpected response: %*ph\n" , + cmd_name, ret, resp); +return -EIO ; + } + +return --retries; + } }static int elants_i2c_calibrate (struct elants_data *ts)
@@ -321,27 +347,20 @@ static u16 elants_i2c_parse_version(u8 *buf)static int elants_i2c_query_hw_version (struct elants_data *ts) {struct i2c_client *client = ts->client; -int error, retry_cnt; +int retry_cnt =MAX_RETRIES ;const u8 cmd[] = {CMD_HEADER_READ ,E_ELAN_INFO_FW_ID ,0x00 ,0x01 };u8 resp[HEADER_SIZE ]; -for (retry_cnt =0 ; retry_cnt <MAX_RETRIES ; retry_cnt++) { - error =elants_i2c_execute_command (client, cmd,sizeof (cmd), - resp,sizeof (resp)); -if (!error) { - ts->hw_version =elants_i2c_parse_version (resp); -if (ts->hw_version !=0xffff ) -return 0 ; - } +while (retry_cnt) { + retry_cnt =elants_i2c_execute_command (client, cmd,sizeof (cmd), + resp,sizeof (resp), + retry_cnt,"read fw id" ); +if (retry_cnt <0 ) +return retry_cnt; -dev_dbg (&client->dev,"read fw id error=%d, buf=%*phC\n" , - error, (int )sizeof (resp), resp); - } - -if (error) { -dev_err (&client->dev, -"Failed to read fw id: %d\n" , error); -return error; + ts->hw_version =elants_i2c_parse_version (resp); +if (ts->hw_version !=0xffff ) +return 0 ; }dev_err (&client->dev,"Invalid fw id: %#04x\n" , ts->hw_version);
@@ -352,26 +371,28 @@ static int elants_i2c_query_hw_version(struct elants_data *ts)static int elants_i2c_query_fw_version (struct elants_data *ts) {struct i2c_client *client = ts->client; -int error, retry_cnt; +int retry_cnt =MAX_RETRIES ;const u8 cmd[] = {CMD_HEADER_READ ,E_ELAN_INFO_FW_VER ,0x00 ,0x01 };u8 resp[HEADER_SIZE ]; -for (retry_cnt =0 ; retry_cnt <MAX_RETRIES ; retry_cnt++) { - error =elants_i2c_execute_command (client, cmd,sizeof (cmd), - resp,sizeof (resp)); -if (!error) { - ts->fw_version =elants_i2c_parse_version (resp); -if (ts->fw_version !=0x0000 && - ts->fw_version !=0xffff ) -return 0 ; - } +while (retry_cnt) { + retry_cnt =elants_i2c_execute_command (client, cmd, +sizeof (cmd), + resp,sizeof (resp), + retry_cnt, +"read fw version" ); +if (retry_cnt <0 ) +return retry_cnt; -dev_dbg (&client->dev,"read fw version error=%d, buf=%*phC\n" , - error, (int )sizeof (resp), resp); + ts->fw_version =elants_i2c_parse_version (resp); +if (ts->fw_version !=0x0000 && ts->fw_version !=0xffff ) +return 0 ; + +dev_dbg (&client->dev,"(read fw version) resp %*phC\n" , + (int )sizeof (resp), resp); } -dev_err (&client->dev, -"Failed to read fw version or fw version is invalid\n" ); +dev_err (&client->dev,"Invalid fw ver: %#04x\n" , ts->fw_version);return -EINVAL ; }
@@ -379,25 +400,20 @@ static int elants_i2c_query_fw_version(struct elants_data *ts)static int elants_i2c_query_test_version (struct elants_data *ts) {struct i2c_client *client = ts->client; -int error, retry_cnt; +int error;u16 version;const u8 cmd[] = {CMD_HEADER_READ ,E_ELAN_INFO_TEST_VER ,0x00 ,0x01 };u8 resp[HEADER_SIZE ]; -for (retry_cnt =0 ; retry_cnt <MAX_RETRIES ; retry_cnt++) { - error =elants_i2c_execute_command (client, cmd,sizeof (cmd), - resp,sizeof (resp)); -if (!error) { - version =elants_i2c_parse_version (resp); - ts->test_version = version >>8 ; - ts->solution_version = version &0xff ; + error =elants_i2c_execute_command (client, cmd,sizeof (cmd), + resp,sizeof (resp),MAX_RETRIES , +"read test version" ); +if (error >=0 ) { + version =elants_i2c_parse_version (resp); + ts->test_version = version >>8 ; + ts->solution_version = version &0xff ; -return 0 ; - } - -dev_dbg (&client->dev, -"read test version error rc=%d, buf=%*phC\n" , - error, (int )sizeof (resp), resp); +return 0 ; }dev_err (&client->dev,"Failed to read test version\n" );
@@ -414,13 +430,10 @@ static int elants_i2c_query_bc_version(struct elants_data *ts)int error; error =elants_i2c_execute_command (client, cmd,sizeof (cmd), - resp,sizeof (resp)); -if (error) { -dev_err (&client->dev, -"read BC version error=%d, buf=%*phC\n" , - error, (int )sizeof (resp), resp); + resp,sizeof (resp),1 , +"read BC version" ); +if (error)return error; - } version =elants_i2c_parse_version (resp); ts->bc_version = version >>8 ;
@@ -452,12 +465,10 @@ static int elants_i2c_query_ts_info(struct elants_data *ts) error =elants_i2c_execute_command (client, get_resolution_cmd,sizeof (get_resolution_cmd), - resp,sizeof (resp)); -if (error) { -dev_err (&client->dev,"get resolution command failed: %d\n" , - error); + resp,sizeof (resp),1 , +"get resolution" ); +if (error)return error; - } rows = resp[2 ] + resp[6 ] + resp[10 ]; cols = resp[3 ] + resp[7 ] + resp[11 ];
@@ -465,36 +476,29 @@ static int elants_i2c_query_ts_info(struct elants_data *ts)/* Process mm_to_pixel information */ error =elants_i2c_execute_command (client, get_osr_cmd,sizeof (get_osr_cmd), - resp,sizeof (resp)); -if (error) { -dev_err (&client->dev,"get osr command failed: %d\n" , - error); + resp,sizeof (resp),1 ,"get osr" ); +if (error)return error; - } osr = resp[3 ]; error =elants_i2c_execute_command (client, get_physical_scan_cmd,sizeof (get_physical_scan_cmd), - resp,sizeof (resp)); -if (error) { -dev_err (&client->dev,"get physical scan command failed: %d\n" , - error); + resp,sizeof (resp),1 , +"get physical scan" ); +if (error)return error; - } phy_x =get_unaligned_be16 (&resp[2 ]); error =elants_i2c_execute_command (client, get_physical_drive_cmd,sizeof (get_physical_drive_cmd), - resp,sizeof (resp)); -if (error) { -dev_err (&client->dev,"get physical drive command failed: %d\n" , - error); + resp,sizeof (resp),1 , +"get physical drive" ); +if (error)return error; - } phy_y =get_unaligned_be16 (&resp[2 ]);
@@ -649,11 +653,10 @@ static int elants_i2c_validate_remark_id(struct elants_data *ts,/* Compare TS Remark ID and FW Remark ID */ error =elants_i2c_execute_command (client, cmd,sizeof (cmd), - resp,sizeof (resp)); -if (error) { -dev_err (&client->dev,"failed to query Remark ID: %d\n" , error); + resp,sizeof (resp), +1 ,"read Remark ID" ); +if (error <0 )return error; - } ts_remark_id =get_unaligned_be16 (&resp[3 ]);
Signature · 1 line
2.20.1
Dmitry Torokhov
maintainerRe: [PATCH v3 5/9] input: elants: refactor elants_i2c_execute_command()
Quoted 81 lines · Michał Mirosław
Apply some DRY-ing to
elants_i2c_execute_command()callers. This pulls polling and error printk()s into a single function.Signed-off-by Michał Mirosław <[email protected]>--- drivers/input/touchscreen/elants_i2c.c | 189 +++++++++++++------------ 1 file changed, 96 insertions(+), 93 deletions(-)drivers/input/touchscreen/elants_i2c.c +33
-18@@ -205,7 +205,8 @@ static int elants_i2c_read(struct i2c_client *client, void *data, size_t size)static int elants_i2c_execute_command (struct i2c_client *client,const u8 *cmd,size_t cmd_size, -u8 *resp,size_t resp_size) +u8 *resp,size_t resp_size, +int retries,const char *cmd_name) {struct i2c_msg msgs[2 ];int ret;@@ -225,30 +226,55 @@ static int elants_i2c_execute_command(struct i2c_client *client,break ;default : -dev_err (&client->dev,"%s: invalid command %*ph\n" , - __func__, (int )cmd_size, cmd); +dev_err (&client->dev,"(%s): invalid command: %*ph\n" , + cmd_name, (int )cmd_size, cmd);return -EINVAL ; } - msgs[0 ].addr = client->addr; - msgs[0 ].flags = client->flags &I2C_M_TEN ; - msgs[0 ].len = cmd_size; - msgs[0 ].buf = (u8 *)cmd; +for (;;) { + msgs[0 ].addr = client->addr; + msgs[0 ].flags = client->flags &I2C_M_TEN ; + msgs[0 ].len = cmd_size; + msgs[0 ].buf = (u8 *)cmd; - msgs[1 ].addr = client->addr; - msgs[1 ].flags = client->flags &I2C_M_TEN ; - msgs[1 ].flags |=I2C_M_RD ; - msgs[1 ].len = resp_size; - msgs[1 ].buf = resp; + msgs[1 ].addr = client->addr; + msgs[1 ].flags = client->flags &I2C_M_TEN ; + msgs[1 ].flags |=I2C_M_RD ; + msgs[1 ].len = resp_size; + msgs[1 ].buf = resp; - ret =i2c_transfer (client->adapter, msgs,ARRAY_SIZE (msgs)); -if (ret <0 ) -return ret; + ret =i2c_transfer (client->adapter, msgs,ARRAY_SIZE (msgs)); +if (ret <0 ) { +if (--retries >0 ) { +dev_dbg (&client->dev, +"(%s) I2C transfer failed: %d (retrying)\n" , + cmd_name, ret); +continue ; + } -if (ret !=ARRAY_SIZE (msgs) || resp[FW_HDR_TYPE ] != expected_response) -return -EIO ; +dev_err (&client->dev, +"(%s) I2C transfer failed: %d\n" , + cmd_name, ret); +return ret; + } -return 0 ; +if (ret !=ARRAY_SIZE (msgs) || + resp[FW_HDR_TYPE ] != expected_response) { +if (--retries >0 ) { +dev_dbg (&client->dev, +"(%s) unexpected response: %*ph (retrying)\n" , + cmd_name, ret, resp);
drivers/input/touchscreen/elants_i2c.c static int elants_i2c_execute_command(struct i2c_client *client, · line 276
Quoted 10 lines
drivers/input/touchscreen/elants_i2c.c +10
-0+continue ; + } + +dev_err (&client->dev, +"(%s) unexpected response: %*ph\n" , + cmd_name, ret, resp); +return -EIO ; + } + +return --retries;
I'd prefer if we returned 0 on success and I'd be OK when flashing firmware to have separate retry counters for the command themselves and for checking the response.
Thanks.
Signature · 1 line
Dmitry
PATCH v3 6/9 input: elants: read touchscreen size for EKTF3624
In reply to Michał MirosławEKTF3624 as present in Asus TF300T tablet has touchscreen size encoded in different registers.
--- drivers/input/touchscreen/elants_i2c.c | 82 ++++++++++++++++++++++++-- 1 file changed, 77 insertions(+), 5 deletions(-)
drivers/input/touchscreen/elants_i2c.c +77 -5
@@ -34,7 +34,7 @@#include <linux/input/mt.h> #include <linux/input/touchscreen.h> #include <linux/acpi.h> -#include <linux/of.h> +#include <linux/of_device.h> #include <linux/gpio/consumer.h> #include <linux/regulator/consumer.h> #include <asm/unaligned.h>
@@ -42,6 +42,10 @@/* Device, Driver information */ #define DEVICE_NAME "elants_i2c" +/* Device IDs */ +#define EKTH3500 0 +#define EKTF3624 1 +/* Convert from rows or columns into resolution */ #define ELAN_TS_RESOLUTION (n, m) (((n) - 1) * (m))
@@ -164,6 +168,7 @@ struct elants_data {bool wake_irq_enabled;bool keep_power_in_suspend; +u8 chip_id;/* Must be last to be used for DMA operations */ u8 buf[MAX_PACKET_SIZE ]____cacheline_aligned ;
@@ -442,7 +447,58 @@ static int elants_i2c_query_bc_version(struct elants_data *ts)return 0 ; } -static int elants_i2c_query_ts_info (struct elants_data *ts) +static int elants_i2c_query_ts_info_ektf (struct elants_data *ts) +{ +struct i2c_client *client = ts->client; +int error; +u8 resp[4 ]; +u16 phy_x, phy_y; +const u8 get_xres_cmd[] = { +CMD_HEADER_READ ,E_INFO_X_RES ,0x00 ,0x00 + }; +const u8 get_yres_cmd[] = { +CMD_HEADER_READ ,E_INFO_Y_RES ,0x00 ,0x00 + }; + +/* Get X/Y size in mm */ + error =elants_i2c_execute_command (client, get_xres_cmd, +sizeof (get_xres_cmd), + resp,sizeof (resp),1 , +"get X size" ); +if (error) +return error; + + phy_x = resp[2 ] | ((resp[3 ] &0xF0 ) <<4 ); + + error =elants_i2c_execute_command (client, get_yres_cmd, +sizeof (get_yres_cmd), + resp,sizeof (resp),1 , +"get Y size" ); +if (error) +return error; + + phy_y = resp[2 ] | ((resp[3 ] &0xF0 ) <<4 ); + +if (!phy_x || !phy_y) { +dev_warn (&client->dev, +"invalid size data: %d x %d mm\n" , + phy_x, phy_y); +return 0 ; + } + +dev_dbg (&client->dev,"phy_x=%d, phy_y=%d\n" , phy_x, phy_y); + +/* calculate resolution from size */ + ts->x_max =2240 -1 ; + ts->x_res =DIV_ROUND_CLOSEST (ts->prop.max_x, phy_x); + + ts->y_max =1408 -1 ; + ts->y_res =DIV_ROUND_CLOSEST (ts->prop.max_y, phy_y); + +return 0 ; +} + +static int elants_i2c_query_ts_info_ekth (struct elants_data *ts) {struct i2c_client *client = ts->client;int error;
@@ -593,8 +649,20 @@ static int elants_i2c_initialize(struct elants_data *ts) error =elants_i2c_query_fw_version (ts);if (!error) error =elants_i2c_query_test_version (ts); -if (!error) - error =elants_i2c_query_ts_info (ts); + +switch (ts->chip_id) { +case EKTH3500 : +if (!error) + error =elants_i2c_query_ts_info_ekth (ts); +break ; +case EKTF3624 : +if (!error) + error =elants_i2c_query_ts_info_ektf (ts); +break ; +default : +unreachable (); +break ; + }if (error) ts->iap_mode =ELAN_IAP_RECOVERY ;
@@ -1245,6 +1313,9 @@ static int elants_i2c_probe(struct i2c_client *client, ts->client = client;i2c_set_clientdata (client, ts); +if (client->dev.of_node) + ts->chip_id = (uintptr_t )of_device_get_match_data (&client->dev); + ts->vcc33 =devm_regulator_get (&client->dev,"vcc33" );if (IS_ERR (ts->vcc33)) { error =PTR_ERR (ts->vcc33);
@@ -1470,7 +1541,8 @@ MODULE_DEVICE_TABLE(acpi, elants_acpi_id);#ifdef CONFIG_OF static const struct of_device_id elants_of_match[] = { - { .compatible ="elan,ekth3500" }, + { .compatible ="elan,ekth3500" , .data = (void *)EKTH3500 }, + { .compatible ="elan,ektf3624" , .data = (void *)EKTF3624 }, {/* sentinel */ } };MODULE_DEVICE_TABLE (of, elants_of_match);
Signature · 1 line
2.20.1
Dmitry Torokhov
maintainerRe: [PATCH v3 6/9] input: elants: read touchscreen size for EKTF3624
Quoted 2 lines · Michał Mirosław
EKTF3624 as present in Asus TF300T tablet has touchscreen size encoded in different registers.
Is this property of chip or property of the device? Johnny, I really need your input here.
Thanks.
Quoted 146 lines
Signed-off-by Michał Mirosław <[email protected]>Reviewed-by Dmitry Osipenko <[email protected]>Tested-by Dmitry Osipenko <[email protected]>--- drivers/input/touchscreen/elants_i2c.c | 82 ++++++++++++++++++++++++-- 1 file changed, 77 insertions(+), 5 deletions(-)drivers/input/touchscreen/elants_i2c.c +77
-5@@ -34,7 +34,7 @@#include <linux/input/mt.h> #include <linux/input/touchscreen.h> #include <linux/acpi.h> -#include <linux/of.h> +#include <linux/of_device.h> #include <linux/gpio/consumer.h> #include <linux/regulator/consumer.h> #include <asm/unaligned.h> @@ -42,6 +42,10 @@/* Device, Driver information */ #define DEVICE_NAME "elants_i2c" +/* Device IDs */ +#define EKTH3500 0 +#define EKTF3624 1 +/* Convert from rows or columns into resolution */ #define ELAN_TS_RESOLUTION (n, m) (((n) - 1) * (m))@@ -164,6 +168,7 @@ struct elants_data {bool wake_irq_enabled;bool keep_power_in_suspend; +u8 chip_id;/* Must be last to be used for DMA operations */ u8 buf[MAX_PACKET_SIZE ]____cacheline_aligned ;@@ -442,7 +447,58 @@ static int elants_i2c_query_bc_version(struct elants_data *ts)return 0 ; } -static int elants_i2c_query_ts_info (struct elants_data *ts) +static int elants_i2c_query_ts_info_ektf (struct elants_data *ts) +{ +struct i2c_client *client = ts->client; +int error; +u8 resp[4 ]; +u16 phy_x, phy_y; +const u8 get_xres_cmd[] = { +CMD_HEADER_READ ,E_INFO_X_RES ,0x00 ,0x00 + }; +const u8 get_yres_cmd[] = { +CMD_HEADER_READ ,E_INFO_Y_RES ,0x00 ,0x00 + }; + +/* Get X/Y size in mm */ + error =elants_i2c_execute_command (client, get_xres_cmd, +sizeof (get_xres_cmd), + resp,sizeof (resp),1 , +"get X size" ); +if (error) +return error; + + phy_x = resp[2 ] | ((resp[3 ] &0xF0 ) <<4 ); + + error =elants_i2c_execute_command (client, get_yres_cmd, +sizeof (get_yres_cmd), + resp,sizeof (resp),1 , +"get Y size" ); +if (error) +return error; + + phy_y = resp[2 ] | ((resp[3 ] &0xF0 ) <<4 ); + +if (!phy_x || !phy_y) { +dev_warn (&client->dev, +"invalid size data: %d x %d mm\n" , + phy_x, phy_y); +return 0 ; + } + +dev_dbg (&client->dev,"phy_x=%d, phy_y=%d\n" , phy_x, phy_y); + +/* calculate resolution from size */ + ts->x_max =2240 -1 ; + ts->x_res =DIV_ROUND_CLOSEST (ts->prop.max_x, phy_x); + + ts->y_max =1408 -1 ; + ts->y_res =DIV_ROUND_CLOSEST (ts->prop.max_y, phy_y); + +return 0 ; +} + +static int elants_i2c_query_ts_info_ekth (struct elants_data *ts) {struct i2c_client *client = ts->client;int error;@@ -593,8 +649,20 @@ static int elants_i2c_initialize(struct elants_data *ts) error =elants_i2c_query_fw_version (ts);if (!error) error =elants_i2c_query_test_version (ts); -if (!error) - error =elants_i2c_query_ts_info (ts); + +switch (ts->chip_id) { +case EKTH3500 : +if (!error) + error =elants_i2c_query_ts_info_ekth (ts); +break ; +case EKTF3624 : +if (!error) + error =elants_i2c_query_ts_info_ektf (ts); +break ; +default : +unreachable (); +break ; + }if (error) ts->iap_mode =ELAN_IAP_RECOVERY ;@@ -1245,6 +1313,9 @@ static int elants_i2c_probe(struct i2c_client *client, ts->client = client;i2c_set_clientdata (client, ts); +if (client->dev.of_node) + ts->chip_id = (uintptr_t )of_device_get_match_data (&client->dev); + ts->vcc33 =devm_regulator_get (&client->dev,"vcc33" );if (IS_ERR (ts->vcc33)) { error =PTR_ERR (ts->vcc33);@@ -1470,7 +1541,8 @@ MODULE_DEVICE_TABLE(acpi, elants_acpi_id);#ifdef CONFIG_OF static const struct of_device_id elants_of_match[] = { - { .compatible ="elan,ekth3500" }, + { .compatible ="elan,ekth3500" , .data = (void *)EKTH3500 }, + { .compatible ="elan,ektf3624" , .data = (void *)EKTF3624 }, {/* sentinel */ } };MODULE_DEVICE_TABLE (of, elants_of_match);Signature · 1 line
2.20.1
Signature · 1 line
Dmitry
PATCH v3 7/9 input: elants: support 0x66 reply opcode for reporting touches
In reply to Michał MirosławFrom: Dmitry Osipenko <[email protected]>
eKTF3624 touchscreen firmware uses two variants of the reply opcodes for reporting touch events: one is 0x63 (used by older firmware) and other is 0x66 (used by newer firmware). The 0x66 variant is equal to 0x63 of eKTH3500, while 0x63 needs small adjustment of the touch pressure value.
Nexus 7 tablet device has eKTF3624 touchscreen and it uses 0x66 opcode for reporting touch events, let's support it now. Other devices, eg. ASUS TF300T, use 0x63.
Note: CMD_HEADER_REK is used for replying to calibration requests, it has the same 0x66 opcode number which eKTF3624 uses for reporting touches. The calibration replies are handled separately from the the rest of the commands in the driver by entering into ELAN_WAIT_RECALIBRATION state and thus this change shouldn't change the old behavior.
--- drivers/input/touchscreen/elants_i2c.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
drivers/input/touchscreen/elants_i2c.c +10 -1
@@ -60,6 +60,15 @@#define QUEUE_HEADER_NORMAL 0X63#define QUEUE_HEADER_WAIT 0x64 +/* +* Depending on firmware version, eKTF3624 touchscreens may utilize one of +* these opcodes for the touch events: 0x63 and 0x66. The 0x63 is used by +* older firmware version and differs from 0x66 such that touch pressure +* value needs to be adjusted. The 0x66 opcode of newer firmware is equal +* to 0x63 of eKTH3500. +*/ +#define QUEUE_HEADER_NORMAL2 0x66 +/* Command header definition */ #define CMD_HEADER_WRITE 0x54#define CMD_HEADER_READ 0x53
@@ -1050,7 +1059,6 @@ static irqreturn_t elants_i2c_irq(int irq, void *_dev)switch (ts->buf[FW_HDR_TYPE ]) {case CMD_HEADER_HELLO :case CMD_HEADER_RESP : -case CMD_HEADER_REK :break ;case QUEUE_HEADER_WAIT :
@@ -1070,6 +1078,7 @@ static irqreturn_t elants_i2c_irq(int irq, void *_dev)break ;case QUEUE_HEADER_NORMAL : +case QUEUE_HEADER_NORMAL2 : report_count = ts->buf[FW_HDR_COUNT ];if (report_count ==0 || report_count >3 ) { dev_err(&client->dev,
Signature · 1 line
2.20.1
Dmitry Torokhov
maintainerRe: [PATCH v3 7/9] input: elants: support 0x66 reply opcode for reporting touches
Quoted 29 lines · Michał Mirosław
From: Dmitry Osipenko <[email protected]>
eKTF3624 touchscreen firmware uses two variants of the reply opcodes for reporting touch events: one is
0x63(used by older firmware) and other is0x66(used by newer firmware). The0x66variant is equal to0x63of eKTH3500, while0x63needs small adjustment of the touch pressure value.Nexus 7 tablet device has eKTF3624 touchscreen and it uses
0x66opcode for reporting touch events, let's support it now. Other devices, eg. ASUS TF300T, use0x63.Note:
CMD_HEADER_REKis used for replying to calibration requests, it has the same0x66opcode number which eKTF3624 uses for reporting touches. The calibration replies are handled separately from the the rest of the commands in the driver by entering intoELAN_WAIT_RECALIBRATIONstate and thus this change shouldn't change the old behavior.Signed-off-by Dmitry Osipenko <[email protected]>Tested-by Michał Mirosław <[email protected]>Signed-off-by Michał Mirosław <[email protected]>--- drivers/input/touchscreen/elants_i2c.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)drivers/input/touchscreen/elants_i2c.c +0
-0
drivers/input/touchscreen/elants_i2c.c line 67
Quoted 8 lines
drivers/input/touchscreen/elants_i2c.c +5
-0@@ -60,6 +60,15 @@#define QUEUE_HEADER_NORMAL 0X63#define QUEUE_HEADER_WAIT 0x64 +/* +* Depending on firmware version, eKTF3624 touchscreens may utilize one of +* these opcodes for the touch events: 0x63 and 0x66. The 0x63 is used by +* older firmware version and differs from 0x66 such that touch pressure +* value needs to be adjusted.
Who is responsible for the adjustment? Where does it happen?
Thanks.
Signature · 1 line
Dmitry
Re: [PATCH v3 7/9] input: elants: support 0x66 reply opcode for reporting touches
26.04.2020 08:15, Dmitry Torokhov пишет:
Quoted 33 lines · Michał Mirosław
Quoted 32 lines
From: Dmitry Osipenko <[email protected]>
eKTF3624 touchscreen firmware uses two variants of the reply opcodes for reporting touch events: one is
0x63(used by older firmware) and other is0x66(used by newer firmware). The0x66variant is equal to0x63of eKTH3500, while0x63needs small adjustment of the touch pressure value.Nexus 7 tablet device has eKTF3624 touchscreen and it uses
0x66opcode for reporting touch events, let's support it now. Other devices, eg. ASUS TF300T, use0x63.Note:
CMD_HEADER_REKis used for replying to calibration requests, it has the same0x66opcode number which eKTF3624 uses for reporting touches. The calibration replies are handled separately from the the rest of the commands in the driver by entering intoELAN_WAIT_RECALIBRATIONstate and thus this change shouldn't change the old behavior.Signed-off-by Dmitry Osipenko <[email protected]>Tested-by Michał Mirosław <[email protected]>Signed-off-by Michał Mirosław <[email protected]>--- drivers/input/touchscreen/elants_i2c.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)drivers/input/touchscreen/elants_i2c.c +0
-0@@ -60,6 +60,15 @@#define QUEUE_HEADER_NORMAL 0X63#define QUEUE_HEADER_WAIT 0x64
Quoted 7 lines
drivers/input/touchscreen/elants_i2c.c
Quoted 5 lines
drivers/input/touchscreen/elants_i2c.c +5
-0+/* +* Depending on firmware version, eKTF3624 touchscreens may utilize one of +* these opcodes for the touch events: 0x63 and 0x66. The 0x63 is used by +* older firmware version and differs from 0x66 such that touch pressure +* value needs to be adjusted. Who is responsible for the adjustment? Where does it happen?
Please see the patch #2 ("support old touch report format") which adds support for parsing of the older packet format that requires the pressure value adjustment.
PATCH v3 8/9 dt-bindings: input: elants-i2c: Document common touchscreen properties
In reply to Michał MirosławFrom: Dmitry Osipenko <[email protected]>
Document support of the common touchscreen properties.
--- Documentation/devicetree/bindings/input/elants_i2c.txt | 4 ++++ 1 file changed, 4 insertions(+)
Documentation/devicetree/bindings/input/elants_i2c.txt +4 -0
@@ -14,9 +14,13 @@ Optional properties: - reset-gpios: reset gpio the chip is connected to. - vcc33-supply: a phandle for the regulator supplying 3.3V power. - vccio-supply: a phandle for the regulator supplying IO power. +- see [2] for additional properties + +For additional optional properties see: touchscreen.txt [0]: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt [1]: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt +[2]: Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt Example: &i2c1 {
Signature · 1 line
2.20.1
PATCH v3 9/9 dt-bindings: input: elants-i2c: Document eKTF3624
In reply to Michał MirosławFrom: Dmitry Osipenko <[email protected]>
The eKTF3624 hardware is similar to eKTH3500.
--- Documentation/devicetree/bindings/input/elants_i2c.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/input/elants_i2c.txt +1 -1
@@ -1,7 +1,7 @@ Elantech I2C Touchscreen Required properties: -- compatible: must be "elan,ekth3500". +- compatible: must be "elan,ekth3500" or "elan,ektf3624". - reg: I2C address of the chip. - interrupts: interrupt to which the chip is connected (see interrupt binding[0]).
Signature · 1 line
2.20.1