From: Michael Welling <mwelling-EkmVulN54Sk@public.gmane.org>
To: dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
vigneshr-l0cyMroinI0@public.gmane.org,
bgriffis-l0cyMroinI0@public.gmane.org,
jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
balbi-l0cyMroinI0@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: GWilson-+8BKOH/0X5NWk0Htik3J/w@public.gmane.org,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: AM335x touchscreen issues
Date: Tue, 26 May 2015 13:11:57 -0500 [thread overview]
Message-ID: <20150526181157.GA8009@deathray> (raw)
Greetings,
I have been porting Linux to a new AM3554 based SoM and have found issues
with the touchscreen reporting touch releases repeatedly to userspace
without actually touching the screen when running ts_calibrate, ts_test
or other graphical touchscreen applications.
This started happening after updating pulling recent changes.
It has also been confirmed to be happening on the beagle bone black:
http://www.spinics.net/lists/linux-iio/msg18580.html
If you look further into this thread you will see a workaround patch that
I came up with:
http://www.spinics.net/lists/linux-iio/msg18583.html
Though this fix stops the reported events in userspace, interrupts are
still occuring repeatedly.
Does anyone have any suggestions beyond what I have done to remedy this
issue?
Regards,
Michael
next reply other threads:[~2015-05-26 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 18:11 Michael Welling [this message]
2015-05-26 18:37 ` AM335x touchscreen issues Felipe Balbi
[not found] ` <20150526183713.GU26599-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-05-26 20:53 ` Michael Welling
2015-05-26 21:15 ` Cooper Jr., Franklin
[not found] ` <8F29D6B095ED194EA1980491A5E029710C89C445-CXzTdvP5/9qIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2015-05-26 21:28 ` Michael Welling
2015-05-26 21:34 ` Cooper Jr., Franklin
[not found] ` <8F29D6B095ED194EA1980491A5E029710C89C4E0-CXzTdvP5/9qIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2015-05-26 21:36 ` Griffis, Brad
[not found] ` <912A29987EAE174BA6CF187D7CDFA9CE270A8C43-YmePFLaaepqIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2015-05-26 21:50 ` Michael Welling
2015-05-26 22:25 ` Griffis, Brad
[not found] ` <912A29987EAE174BA6CF187D7CDFA9CE270A8D48-YmePFLaaepqIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2015-05-26 22:46 ` Michael Welling
2015-05-26 22:31 ` Cooper Jr., Franklin
[not found] ` <8F29D6B095ED194EA1980491A5E029710C89C70D-CXzTdvP5/9qIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2015-05-26 23:06 ` Michael Welling
2015-05-26 23:37 ` Cooper Jr., Franklin
2015-05-27 4:06 ` Vignesh R
2015-05-27 17:29 ` Michael Welling
2015-05-26 21:41 ` Michael Welling
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=20150526181157.GA8009@deathray \
--to=mwelling-ekmvuln54sk@public.gmane.org \
--cc=GWilson-+8BKOH/0X5NWk0Htik3J/w@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=bgriffis-l0cyMroinI0@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vigneshr-l0cyMroinI0@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).