public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Welling <mwelling@ieee.org>
To: dmitry.torokhov@gmail.com, vigneshr@ti.com, bgriffis@ti.com,
	jic23@kernel.org, wsa@the-dreams.de, balbi@ti.com,
	linux-input@vger.kernel.org
Cc: GWilson@sakuraus.com, linux-iio@vger.kernel.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

             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
2015-05-26 20:53   ` Michael Welling
2015-05-26 21:15     ` Cooper Jr., Franklin
2015-05-26 21:28       ` Michael Welling
2015-05-26 21:34         ` Cooper Jr., Franklin
2015-05-26 21:36           ` Griffis, Brad
2015-05-26 21:50             ` Michael Welling
2015-05-26 22:25               ` Griffis, Brad
2015-05-26 22:46                 ` Michael Welling
2015-05-26 22:31               ` Cooper Jr., Franklin
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@ieee.org \
    --cc=GWilson@sakuraus.com \
    --cc=balbi@ti.com \
    --cc=bgriffis@ti.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=vigneshr@ti.com \
    --cc=wsa@the-dreams.de \
    /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