From: Marek Vasut <marex@denx.de>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Vipul Kumar Samar <vipulkumar.samar@st.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Bill Pemberton <wfp5p@virginia.edu>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] input: stmpe: Fix the touchscreen interrupt handling
Date: Tue, 18 Jun 2013 14:01:13 +0200 [thread overview]
Message-ID: <201306181401.13755.marex@denx.de> (raw)
In-Reply-To: <20130618085035.GD7161@zurbaran>
Hi,
> Hi Marek,
>
> On Fri, May 17, 2013 at 01:25:11AM +0200, Marek Vasut wrote:
> > Dear Samuel Ortiz,
> >
> > > Hi Marek,
> > >
> > > On Mon, Apr 22, 2013 at 01:06:05AM +0200, Marek Vasut wrote:
> > > > The touchscreen interrupt handling in the STMPE touchscreen driver
> > > > doesn't seem to work correctly. It relies on FIFO_TH to be asserted
> > > > instead of TOUCH_DET interrupt for touchscreen detection.
> > > >
> > > > The FIFO_TH is usually asserted but is asserted independently of the
> > > > touchscreen controller operation. Because the bits in the interrupt
> > > > status register are not entirely cleaned, the interrupt handler is
> > > > triggered even if FIFO_TH is not yet set. Make sure that all bits in
> > > > the interrupt status register are cleared early.
> > > >
> > > > Rework the touchscreen interrupt handling so it waits for TOUCH_DET
> > > > interrupt to happen. Upon first TOUCH_DET interrupt, worker thread
> > > > is started which polls the touchscreen controller for location data
> > > > until no touch is detected. Touch is determined by checking the X
> > > > and Y coordinates, if they are zero, no touch happens.
> > > >
> > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > > Cc: Samuel Ortiz <sameo@linux.intel.com>
> > > > Cc: Vipul Kumar Samar <vipulkumar.samar@st.com>
> > > > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > > > Cc: Bill Pemberton <wfp5p@virginia.edu>
> > > > Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > > > ---
> > > >
> > > > drivers/input/touchscreen/stmpe-ts.c | 111
> > > > ++++++++++++++-------------------- drivers/mfd/stmpe.c
> > > >
> > > > | 10 +--
> > > >
> > > > 2 files changed, 50 insertions(+), 71 deletions(-)
> > >
> > > Could you please split this patch in 2, the MFD part is independent
> > > from the input one and could be applied separately.
> >
> > I'd vote for applying this as one single patch, since this fixes one
> > single problem (touchscreen not working properly). Or is that a big
> > issue for you?
>
> I am fine as long as we get feedback from Dmitry and the ST folks about
> it.
Absoluty, the feedback from the ST guys is completely imperative in this case.
Thank you!
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-06-18 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 23:06 [PATCH] input: stmpe: Fix the touchscreen interrupt handling Marek Vasut
2013-05-16 22:17 ` Samuel Ortiz
2013-05-16 23:25 ` Marek Vasut
2013-06-18 8:50 ` Samuel Ortiz
2013-06-18 12:01 ` Marek Vasut [this message]
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=201306181401.13755.marex@denx.de \
--to=marex@denx.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=vipulkumar.samar@st.com \
--cc=viresh.kumar@linaro.org \
--cc=wfp5p@virginia.edu \
/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.