Re: Goodix touchscreen works intermittently, fails reading config info.

Started by Brad Baker on Sep 12, 2016 · 5 messages from 3 authors · Last reply Oct 12, 2016

open the first message on its own page

Message details and related content
Irina,
  The user just reported... "the TS is not working every time, here is
a log from when it is not working". The below logging appears to show
that setting the default trigger_type=0 when read_config fails does
not make a difference.  His statement that it's not working *every
time* is curious because he said before it was working like 9 out of
10 times he booted up.

http://pastebin.com/hpWbgpTe
[   10.922484] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   10.927791] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0
[   10.927797] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[   10.927912] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   10.928112] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6

source: https://github.com/blocksonic/gt9xx/blob/device-tree/goodix.c

I'm waiting for him to send the ACPI table data you requested.  I was
not sure exactly how to do this. I asked him to run this series of
commands which worked on my machine.  Is it OK?

mkdir ~/acpitables
cd /sys/firmware/acpi/tables/
for i in * ; do sudo cat $i > ~/acpitables/$i.dat; done
cd ~/acpitables
for i in * ; do iasl -d $i ; done
cat *.dsl >> chuwi_hi12_acpi.dsl

Also: following is an older log prior to my code changes where
read_config was succeeding but the user reported the touchscreen was
registering touch events in the wrong place.  This may have been some
fluke as he has not been reporting this type of problem happening
often or since.  Also appended to the end of this log is output from
dmidecode if it's  helpful:  http://pastebin.com/6QWF6JB8


On Sun, Sep 11, 2016 at 4:28 PM, Brad Baker [off-list ref] wrote:
Hi Irina,
  I don't have the tablet. The user's last reply yesterday was this:
"here is a log of the, TS working with your latest edits
http://pastebin.com/mhMpa3Zj . it might be a couple days before i can
do much more testing on it.  "
So I'm still waiting to find out if my changing the default
trigger_type=0 had any effect when read_config fails.
That log of the working case shows things as expected.

[   12.356637] goodix_backport: loading out-of-tree module taints kernel.
[   12.356739] goodix_backport: module verification failed: signature
and/or required key missing - tainting kernel
[   12.364644] intel_sst_acpi 808622A8:00: No matching machine driver found
[   12.365892] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   12.373813] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   12.373822] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   12.373998] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6



On Sun, Sep 11, 2016 at 3:54 PM, Tirdea, Irina [off-list ref] wrote:
quoted
quoted
-----Original Message-----
From: <redacted> [mailto:<redacted>] On Behalf Of Brad Baker
Sent: 11 September, 2016 0:21
To: bastien nocera
Cc: <redacted>
Subject: Goodix touchscreen works intermittently, fails reading config info.

Summary: Goodix touchscreen works intermittently, fails reading config info.
 https://bugzilla.kernel.org/show_bug.cgi?id=156511

Description:  Chuwi Hi12 tablet with Intel cherry-trail Atom Z8300,
the touchscreen does work after bootup most of the time, but sometimes
it does not work without running modprobe.  When it fails the dmesg
log shows the error "Invalid config, using defaults" and when it works

38 more quoted lines

Message details and related content
Irina, here is the ACPI table data you requested for this device
(Chuwi Hi12 tablet) : http://pastebin.com/84cjD8kp

On Mon, Sep 12, 2016 at 2:32 PM, Brad Baker [off-list ref] wrote:
Irina,
  The user just reported... "the TS is not working every time, here is
a log from when it is not working". The below logging appears to show
that setting the default trigger_type=0 when read_config fails does
not make a difference.  His statement that it's not working *every
time* is curious because he said before it was working like 9 out of
10 times he booted up.

http://pastebin.com/hpWbgpTe
[   10.922484] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   10.927791] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0
[   10.927797] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[   10.927912] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   10.928112] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6

source: https://github.com/blocksonic/gt9xx/blob/device-tree/goodix.c

I'm waiting for him to send the ACPI table data you requested.  I was
not sure exactly how to do this. I asked him to run this series of
commands which worked on my machine.  Is it OK?

mkdir ~/acpitables
cd /sys/firmware/acpi/tables/
for i in * ; do sudo cat $i > ~/acpitables/$i.dat; done
cd ~/acpitables
for i in * ; do iasl -d $i ; done
cat *.dsl >> chuwi_hi12_acpi.dsl

Also: following is an older log prior to my code changes where
read_config was succeeding but the user reported the touchscreen was
registering touch events in the wrong place.  This may have been some
fluke as he has not been reporting this type of problem happening
often or since.  Also appended to the end of this log is output from
dmidecode if it's  helpful:  http://pastebin.com/6QWF6JB8


On Sun, Sep 11, 2016 at 4:28 PM, Brad Baker [off-list ref] wrote:

78 more quoted lines

Message details and related content
Irina, a little more info on the symptoms. The user reports the
touchscreen works when restarting but fails when powering on.  He says
pretty much 100% of the time.  The log is the same...

http://pastebin.com/25haaPQd
[   10.246074] goodix_backport: loading out-of-tree module taints kernel.
[   10.246172] goodix_backport: module verification failed: signature
and/or required key missing - tainting kernel
[   10.263788] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   10.270135] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0
[   10.270141] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[   10.270258] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   10.270608] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6

On Mon, Sep 12, 2016 at 2:32 PM, Brad Baker [off-list ref] wrote:
Irina,
  The user just reported... "the TS is not working every time, here is
a log from when it is not working". The below logging appears to show
that setting the default trigger_type=0 when read_config fails does
not make a difference.  His statement that it's not working *every
time* is curious because he said before it was working like 9 out of
10 times he booted up.

http://pastebin.com/hpWbgpTe
[   10.922484] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   10.927791] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0
[   10.927797] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[   10.927912] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   10.928112] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6

source: https://github.com/blocksonic/gt9xx/blob/device-tree/goodix.c

I'm waiting for him to send the ACPI table data you requested.  I was
not sure exactly how to do this. I asked him to run this series of
commands which worked on my machine.  Is it OK?

mkdir ~/acpitables
cd /sys/firmware/acpi/tables/
for i in * ; do sudo cat $i > ~/acpitables/$i.dat; done
cd ~/acpitables
for i in * ; do iasl -d $i ; done
cat *.dsl >> chuwi_hi12_acpi.dsl

Also: following is an older log prior to my code changes where
read_config was succeeding but the user reported the touchscreen was
registering touch events in the wrong place.  This may have been some
fluke as he has not been reporting this type of problem happening
often or since.  Also appended to the end of this log is output from
dmidecode if it's  helpful:  http://pastebin.com/6QWF6JB8


On Sun, Sep 11, 2016 at 4:28 PM, Brad Baker [off-list ref] wrote:

78 more quoted lines

Message details and related content
-----Original Message-----
From: <redacted> [mailto:<redacted>] On Behalf Of Brad Baker
Sent: 13 September, 2016 6:05
To: Tirdea, Irina
Cc: bastien nocera; <redacted>
Subject: Re: Goodix touchscreen works intermittently, fails reading config info.

Irina, a little more info on the symptoms. The user reports the
touchscreen works when restarting but fails when powering on.  He says
pretty much 100% of the time.  The log is the same...
Hi Brad,

Thanks for all the information you provided. I have already replied on the
Bugzilla thread with some patches that enable reset for the device.

Regards,
Irina

http://pastebin.com/25haaPQd
[   10.246074] goodix_backport: loading out-of-tree module taints kernel.
[   10.246172] goodix_backport: module verification failed: signature
and/or required key missing - tainting kernel
[   10.263788] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   10.270135] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0
[   10.270141] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[   10.270258] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   10.270608] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6
Message details and related content
Hello from ;-) Chuwi tablets warrior.
Actually have done all requested, .cfg, bin, working module, etc are
located : https://gitlab.com/SergK/chuwi_hi12/tree/master.

Many thanks and regards,
                             Serge Kolotylo.


On Wed, Sep 14, 2016 at 9:29 AM, Tirdea, Irina [off-list ref] wrote:
quoted
-----Original Message-----
From: <redacted> [mailto:<redacted>] On Behalf Of Brad Baker
Sent: 13 September, 2016 6:05
To: Tirdea, Irina
Cc: bastien nocera; <redacted>
Subject: Re: Goodix touchscreen works intermittently, fails reading config info.

Irina, a little more info on the symptoms. The user reports the
touchscreen works when restarting but fails when powering on.  He says
pretty much 100% of the time.  The log is the same...
Hi Brad,

Thanks for all the information you provided. I have already replied on the
Bugzilla thread with some patches that enable reset for the device.

Regards,
Irina

quoted
http://pastebin.com/25haaPQd
[   10.246074] goodix_backport: loading out-of-tree module taints kernel.
[   10.246172] goodix_backport: module verification failed: signature
and/or required key missing - tainting kernel
[   10.263788] Goodix-TS i2c-GDIX1001:00: ID 9111, version: 1060
[   10.270135] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0
[   10.270141] Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
[   10.270258] Goodix-TS i2c-GDIX1001:00: dev_info: cfg_len: 186,
x_max: 2160, y_max: 2160, touch_num: 10, trigger_type: 0
[   10.270608] input: Goodix Capacitive TouchScreen as
/devices/pci0000:00/808622C1:05/i2c-13/i2c-GDIX1001:00/input/input6
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help