WIN touch button not working

[aleksey1831981]

Hello.
My native language is not English, so I apologize in advance for possible spelling errors.

The Chinese industry has released many different brands of touchpads to the global market.

I have DEXP URSUS KX310 tablet at hand. Basically, this brand is represented on the Russian market. This is a typical Bay-Trail tablet. Has a touch WIN button.

When trying to extract the driver from the Windows driver, and install the modified Silead, it worked. But I ran into a problem: the WIN touch button does not work. The touchpad also has an inactive area (band) in the middle of the screen.

While trying to find a similar topic to discuss porting drivers to Linux, I noticed that the operation of the touch WIN button on touchpads is not discussed in the Linux community.

I found that the TouchSetting.gt file that makes this button work on Windows looks like this:

[Setting]
;UpdateCFG=1
SendCFG=1		;Send CFG to touch IC when loading driver	
SleepDisable=0
PhysicalXsize=2170	;Physical size,the unit is 0.1mm
PhysicalYsize=1357

[Support]
ESD=1		;Driver supports ESD recovery processing
;SensorID=0	;According to the different SensorID send different configuration
GtpTool=0	;GuitarTestPlateform tool support
X2X=0
Y2Y=0
X2Y=0
Log=0

[Feature]
Pen=		;stylus/pen support
NumberOfKey=1	;The total number of keys supported,equal to 0 does not support key
Key1=0xe3	;0xe3 is home key,Must be a hexadecimal number
Key2=
Key3=
Key4=

[CFG]
DefultCFG=0x00,0x9C,0x0E,0x60,0x09,0x0A,0x3D,0x01,0x01,0x08,0x28,0x0F,0x5A,0x3C,0x03,0x05,0x00,0x00,0x00,0x00,0x00,0x00,0x08,0x19,0x1C,0x1E,0x14,0x90,0x2E,0xAA,0x28,0x2A,0x33,0x0F,0x00,0x00,0x00,0x01,0x03,0x25,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0x00,0x00,0x1E,0x50,0x94,0xC5,0x02,0x07,0x00,0x00,0x04,0x8F,0x21,0x00,0x80,0x28,0x00,0x74,0x31,0x00,0x6C,0x3B,0x00,0x68,0x48,0x00,0x68,0x08,0x00,0x00,0x00,0xF0,0x5A,0x40,0x70,0x00,0x17,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x19,0x18,0x17,0x16,0x15,0x14,0x11,0x10,0x0F,0x0E,0x0D,0x0C,0x09,0x08,0x07,0x06,0x05,0x04,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x04,0x06,0x07,0x08,0x0A,0x0C,0x0D,0x0E,0x0F,0x10,0x11,0x12,0x13,0x14,0x19,0x1B,0x1C,0x1E,0x1F,0x20,0x21,0x22,0x23,0x24,0x25,0x26,0x27,0x2A,0xFF,0xFF,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xF4,0x01
senserid_0=0x00,0x9C,0x0E,0x60,0x09,0x0A,0x3D,0x01,0x01,0x08,0x28,0x0F,0x5A,0x3C,0x03,0x05,0x00,0x00,0x00,0x00,0x00,0x00,0x08,0x19,0x1C,0x1E,0x14,0x90,0x2E,0xAA,0x28,0x2A,0x33,0x0F,0x00,0x00,0x00,0x01,0x03,0x25,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x07,0x00,0x00,0x1E,0x50,0x94,0xC5,0x02,0x07,0x00,0x00,0x04,0x8F,0x21,0x00,0x80,0x28,0x00,0x74,0x31,0x00,0x6C,0x3B,0x00,0x68,0x48,0x00,0x68,0x08,0x00,0x00,0x00,0xF0,0x5A,0x40,0x70,0x00,0x17,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x19,0x18,0x17,0x16,0x15,0x14,0x11,0x10,0x0F,0x0E,0x0D,0x0C,0x09,0x08,0x07,0x06,0x05,0x04,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x04,0x06,0x07,0x08,0x0A,0x0C,0x0D,0x0E,0x0F,0x10,0x11,0x12,0x13,0x14,0x19,0x1B,0x1C,0x1E,0x1F,0x20,0x21,0x22,0x23,0x24,0x25,0x26,0x27,0x2A,0xFF,0xFF,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xF4,0x01
senserid_1=
senserid_2=
senserid_3=
senserid_4=
senserid_5=

I also noticed that in some discussions it was mentioned that Linux drivers for Goodix touchpads have a similar structure. But it looks like Goodix enthusiasts don't know what they're talking about.

Can someone help me understand the driver change algorithm? If not, who can I contact?