New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 675803 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Clapper touchscreen: config update error in 4.4 kernel

Project Member Reported by kathrelk...@chromium.org, Dec 20 2016

Issue description

Example failure on clapper:
https://wmatrix.googleplex.com/testrun/unfiltered?test_ids=400355588

Started happening in R57-9035.0.0, which is conveniently the very same build that clapper switched over to 4.4 kernel.  Happens every time.


2016-12-19T13:46:41.351766+00:00 NOTICE chromeos-atmel-touch-config-update[1389]: error: No T19_Status for /sys/bus/i2c/devices/i2c-ATML0001:01
2016-12-19T13:46:41.368604+00:00 NOTICE chromeos-atmel-touch-config-update[1391]: Using ts_config_mapping to find config 'error: No T19_Status for /sys/bus/i2c/devices/i2c-ATML0001:01'
2016-12-19T13:46:41.383306+00:00 NOTICE chromeos-atmel-touch-config-update[1394]: error: No valid config file with name error: No T19_Status for /sys/bus/i2c/devices/i2c-ATML0001:01 found.
2016-12-19T13:46:41.384646+00:00 NOTICE chromeos-touch-update[996]: ATML0001:01 config update failed.
 
It looks like the version of the atmel_mxt_ts driver in kernels 4.4 and 3.18 are missing a patch that adds in a new sysfs entry:

https://chromium-review.googlesource.com/#/c/200814/
Cc: kathrelk...@chromium.org
Status: Started (was: Untriaged)
I think we need these cherry picks to fix this for 3.18 and 4.4

v3.18 = https://chromium-review.googlesource.com/#/c/422413/
v4.4  = https://chromium-review.googlesource.com/#/c/422573/
I just built a kernel with this patch and the error seemed to go away.  I'll try to merge these in asap
Status: Fixed (was: Started)
I just downloaded the newest official build and booted my Clapper on it.  Everything appears to be working smoothly now.  I believe this is fixed.

(Should be fixed on any builds >=9149.0.0, I actually tested it on 9150.0.0 though)
Status: Verified (was: Fixed)

Sign in to add a comment