[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130805192113.GA7041@gmail.com>
Date: Mon, 5 Aug 2013 20:21:14 +0100
From: "Zubair Lutfullah :" <zubair.lutfullah@...il.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: "Zubair Lutfullah :" <zubair.lutfullah@...il.com>,
Jonathan Cameron <jic23@...nel.org>, jic23@....ac.uk,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-input@...r.kernel.org, gregkh@...uxfoundation.org,
Russ.Dill@...com
Subject: Re: [PATCH 1/2] input: ti_tsc: Enable shared IRQ for TSC
On Mon, Aug 05, 2013 at 10:40:31AM -0700, Dmitry Torokhov wrote:
> >
> > FIFO 1 used only by ADC and FIFO1THRES handler is inside the iio/adc driver
> > FIFO 0 used only by TSC and FIFO0THRES handler is inside the input/touchscreen
> >
> > Note: These are level interrupts.
> >
> > I would like some input on how to handle such a situation.
>
> It looks like you need to have smart demultiplexing in MFD core of your
> driver instead of relying on shared interrupt handler.
>
> Another option would be to check "your" bits, handle the data, clear the
> status and then check bits again and return IRQ_NONE instead of
> IRQ_HANDLED if other guys bits are set, but it is way too ugly.
>
> Thanks.
>
> --
> Dmitry
That is going to make a lot of changes in mfd, input and iio
And should require a separate patch series.
Is it possible to accept the current patches to add continuous mode
to the ADC side as is before the next merge window?
This issue doesn't disturb each side individually..
I'll look into fixing the IRQs after settling continuous mode.
Thanks
Zubair Lutfullah
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists