From: Andre <andre.muller@web.de>
To: Nick Dyer <nick.dyer@itdev.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"George G. Davis" <george_davis@mentor.com>,
Jiada Wang <jiada_wang@mentor.com>,
linux-kernel@vger.kernel.org
Subject: [Regression]: Commit 74d905d2 breaks the touchpad and touchscreen of Google Chromebook "samus"
Date: Wed, 4 Nov 2020 09:13:45 +0100 [thread overview]
Message-ID: <735253bd-5500-2b8d-c98d-99bddb0617ce@web.de> (raw)
Hi,
commit 74d905d2: Input: atmel_mxt_ts - only read messages in
mxt_acquire_irq() when necessary
breaks the touchpad and touchscreen of the 2015 Chromebook Pixel "Samus".
Reverting the commit from the current git tree gets them to work again.
I am not at all shure what info to include, but I will happily provide
it on request.
The dmesgs of a boot with commit 74d905d2 show "Enabling RETRIGEN
workaround", but otherwise looks the same as a boot without.
Here is the relevant bit (with 74d905d2):
atmel_mxt_ts i2c-ATML0000:01: Family: 164 Variant: 17 Firmware V1.0.AA
Objects: 32
atmel_mxt_ts i2c-ATML0000:01: Enabling RETRIGEN workaround
atmel_mxt_ts i2c-ATML0000:01: Direct firmware load for maxtouch.cfg
failed with error -2
atmel_mxt_ts i2c-ATML0000:01: Touchscreen size X960Y540
input: Atmel maXTouch Touchpad as
/devices/pci0000:00/INT3432:00/i2c-0/i2c-ATML0000:01/input/input4
atmel_mxt_ts i2c-ATML0001:01: Family: 164 Variant: 13 Firmware V1.0.AA
Objects: 41
atmel_mxt_ts i2c-ATML0001:01: Enabling RETRIGEN workaround
atmel_mxt_ts i2c-ATML0001:01: Direct firmware load for maxtouch.cfg
failed with error -2
Thank you,
Andre Müller
next reply other threads:[~2020-11-04 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 8:13 Andre [this message]
2020-11-05 13:25 ` Wang, Jiada
2020-11-05 14:23 ` Andre Muller
2020-11-24 3:02 ` Wang, Jiada
2020-11-24 6:15 ` Andre Muller
2020-11-24 6:32 ` Wang, Jiada
2020-11-24 8:07 ` Andre Muller
2020-11-23 23:27 ` Linus Walleij
2020-11-28 12:53 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=735253bd-5500-2b8d-c98d-99bddb0617ce@web.de \
--to=andre.muller@web.de \
--cc=dmitry.torokhov@gmail.com \
--cc=george_davis@mentor.com \
--cc=jiada_wang@mentor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.dyer@itdev.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®