From: "Zubair Lutfullah :" <zubair.lutfullah@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Zubair Lutfullah <zubair.lutfullah@gmail.com>,
jic23@cam.ac.uk, dmitry.torokhov@gmail.com,
sameo@linux.intel.com, lee.jones@linaro.org,
linux-iio@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
Russ.Dill@ti.com
Subject: Re: [PATCH 3/4] input: ti_tsc: Enable shared IRQ for TSC and add overrun, underflow checks
Date: Fri, 16 Aug 2013 22:31:33 +0100 [thread overview]
Message-ID: <20130816213132.GD2636@gmail.com> (raw)
In-Reply-To: <20130816091409.GC26895@linutronix.de>
On Fri, Aug 16, 2013 at 11:14:09AM +0200, Sebastian Andrzej Siewior wrote:
> * Zubair Lutfullah | 2013-08-13 17:48:18 [+0100]:
> >+ if ((status & IRQENB_FIFO0OVRRUN) ||
> >+ (status & IRQENB_FIFO0UNDRFLW)) {
> >+
> >+ config = titsc_readl(ts_dev, REG_CTRL);
> >+ config &= ~(CNTRLREG_TSCSSENB);
> >+ titsc_writel(ts_dev, REG_CTRL, config);
> >+
> >+ if (status & IRQENB_FIFO0UNDRFLW) {
> >+ titsc_writel(ts_dev, REG_IRQSTATUS,
> >+ (status | IRQENB_FIFO0UNDRFLW));
> >+ irqclr |= IRQENB_FIFO0UNDRFLW;
> >+ } else {
> >+ titsc_writel(ts_dev, REG_IRQSTATUS,
> >+ (status | IRQENB_FIFO0OVRRUN));
> >+ irqclr |= IRQENB_FIFO0OVRRUN;
> >+ }
>
> You don't do anything on overflow / underflow. Is this due to the fact
> once enabled for FIFO1 it also triggers for FIFO0?
>
The TSCADC module doesn't recover from these interrupts.
> >+ titsc_writel(ts_dev, REG_CTRL,
> >+ (config | CNTRLREG_TSCSSENB));
The fix is to re-enable the module after disabling
and clearing the interrupts.
That is what the handler is doing.
> >+ } else if (status & IRQENB_FIFO0THRES) {
> > titsc_read_coordinates(ts_dev, &x, &y, &z1, &z2);
> >
> > if (ts_dev->pen_down && z1 != 0 && z2 != 0) {
> >@@ -317,9 +342,11 @@ static irqreturn_t titsc_irq(int irq, void *dev)
> > }
> >
> > if (irqclr) {
> >- titsc_writel(ts_dev, REG_IRQSTATUS, irqclr);
> >+ titsc_writel(ts_dev, REG_IRQSTATUS, (status | irqclr));
>
> Shouldn't FIFO1UNDRFLW & OVRRUN be handled by the adc driver? Why do you
> or the unhandled bits as well here?
FIFO1 is only used by TSC. ADC doesn't touch it.
>
> > am335x_tsc_se_set(ts_dev->mfd_tscadc, ts_dev->step_mask);
> >- return IRQ_HANDLED;
> >+ status = titsc_readl(ts_dev, REG_IRQSTATUS);
> >+ if (status == false)
> >+ return IRQ_HANDLED;
>
> And why this? If you something you handled it, if you didn't you return
> NONE. Why does it depend on REG_IRQSTATUS?
These quirks are to handle the situation where both IRQs happen
simultaneously. Which can occur when someone is using the TSC
while continuously sampling using the ADC.
REG_IRQSTATUS has flags for FIFO0 used by ADC as well.
If there are still those IRQs to handle, then IRQ_NONE is returned.
Otherwise, all IRQ flags are clear so IRQ_HANDLED is returned.
Thanks
Zubair
next prev parent reply other threads:[~2013-08-16 22:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 16:48 [PATCH 0/4] iio: input: ti_am335x_adc: Add continuous sampling support round 4 Zubair Lutfullah
2013-08-13 16:48 ` [PATCH 1/4] input: ti_am335x_tsc: correct step mask update after IRQ Zubair Lutfullah
2013-08-16 8:53 ` Sebastian Andrzej Siewior
2013-08-16 21:42 ` Zubair Lutfullah :
2013-08-13 16:48 ` [PATCH 2/4] input: ti_am335x_tsc: Increase sequencer delay time Zubair Lutfullah
2013-08-16 9:04 ` Sebastian Andrzej Siewior
2013-08-13 16:48 ` [PATCH 3/4] input: ti_tsc: Enable shared IRQ for TSC and add overrun, underflow checks Zubair Lutfullah
2013-08-13 17:07 ` Lee Jones
[not found] ` <1376412499-21007-4-git-send-email-zubair.lutfullah-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-16 9:14 ` Sebastian Andrzej Siewior
2013-08-16 21:31 ` Zubair Lutfullah : [this message]
2013-08-13 16:48 ` [PATCH 4/4] iio: ti_am335x_adc: Add continuous sampling and trigger support Zubair Lutfullah
2013-08-13 17:05 ` Lee Jones
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=20130816213132.GD2636@gmail.com \
--to=zubair.lutfullah@gmail.com \
--cc=Russ.Dill@ti.com \
--cc=bigeasy@linutronix.de \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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 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).