From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: mutt@amd.karlin.mff.cuni.cz,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org,
nick@shmanahar.org, rydberg@bitmath.org,
linux-input@vger.kernel.org, bleung@google.com
Subject: Re: atmel_mxt_ts on droid4: powersave seems to break the driver
Date: Tue, 17 Apr 2018 21:39:03 +0200 [thread overview]
Message-ID: <20180417193903.GA11082@amd> (raw)
In-Reply-To: <20180417182021.GA67621@dtor-ws>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
Hi!
> > v4.17-rc1 on motorola droid 4.
> >
> > If I disable/reenable touschreen with xinput, it fails, with this in
> > the logs:
> >
> > [ 1633.749450] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
> > [ 1655.938751] atmel_mxt_ts 1-004a: __mxt_read_reg: i2c transfer
> > failed (-121)
> > [ 1655.945800] atmel_mxt_ts 1-004a: Failed to read T44 and T5 (-121)
> > [ 1663.829498] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
> >
> > Unfortunately, xscreensaver seems to break it in a similar way.
> >
>
> There were a few changes to the Atmel driver, ending with commit
> 96a938aa214e965d5b4a2f10443b29cad14289b9, but they mostly dealt with
> removal of platform data and moving to generic device properties...
> Can you try bisecting this series:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git ib-chrome-platform-input-atmel-mx-ts-platform-removal
>
To avoid any misunderstanding, I'm not saying this is
regression from v4.16. I did some testing on v4.16 (and it was first
kernel to work there at all), but I did not have good enough userland
to play with touchscreen disable/enable.
Plus, I'm not sure this is 100% reproducible, let me play some more.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: atmel_mxt_ts on droid4: powersave seems to break the driver
Date: Tue, 17 Apr 2018 21:39:03 +0200 [thread overview]
Message-ID: <20180417193903.GA11082@amd> (raw)
In-Reply-To: <20180417182021.GA67621@dtor-ws>
Hi!
> > v4.17-rc1 on motorola droid 4.
> >
> > If I disable/reenable touschreen with xinput, it fails, with this in
> > the logs:
> >
> > [ 1633.749450] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
> > [ 1655.938751] atmel_mxt_ts 1-004a: __mxt_read_reg: i2c transfer
> > failed (-121)
> > [ 1655.945800] atmel_mxt_ts 1-004a: Failed to read T44 and T5 (-121)
> > [ 1663.829498] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
> >
> > Unfortunately, xscreensaver seems to break it in a similar way.
> >
>
> There were a few changes to the Atmel driver, ending with commit
> 96a938aa214e965d5b4a2f10443b29cad14289b9, but they mostly dealt with
> removal of platform data and moving to generic device properties...
> Can you try bisecting this series:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git ib-chrome-platform-input-atmel-mx-ts-platform-removal
>
To avoid any misunderstanding, I'm not saying this is
regression from v4.16. I did some testing on v4.16 (and it was first
kernel to work there at all), but I did not have good enough userland
to play with touchscreen disable/enable.
Plus, I'm not sure this is 100% reproducible, let me play some more.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180417/986931f0/attachment.sig>
next prev parent reply other threads:[~2018-04-17 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 7:38 atmel_mxt_ts on droid4: powersave seems to break the driver Pavel Machek
2018-04-17 7:38 ` Pavel Machek
2018-04-17 18:20 ` Dmitry Torokhov
2018-04-17 18:20 ` Dmitry Torokhov
2018-04-17 19:39 ` Pavel Machek [this message]
2018-04-17 19:39 ` Pavel Machek
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=20180417193903.GA11082@amd \
--to=pavel@ucw.cz \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=mutt@amd.karlin.mff.cuni.cz \
--cc=nekit1000@gmail.com \
--cc=nick@shmanahar.org \
--cc=rydberg@bitmath.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.