RE: mfd regmap irq to handle some cases

[Ashish Jangam <Ashish.Jangam@kpitcummins.com>]

________________________________________
From: Mark Brown [broonie@opensource.wolfsonmicro.com]
Sent: Monday, January 23, 2012 8:48 PM
To: Ashish Jangam
Cc: linux-kernel@vger.kernel.org
Subject: Re: mfd regmap irq to handle some cases

On Mon, Jan 23, 2012 at 07:03:31PM +0530, Ashish Jangam wrote:
> On Mon, 2012-01-23 at 19:02 +0530, Ashish Jangam wrote:

> > > > approach for some variants of DA9052 and DA9053 when event is cleared
> > > > a spurious interrupt gets generated therefore in earlier release of
> > > > DA9052/53 MFD module a delay was added. Therefore we need to think on
> > > > how to handle such cases in regmap irq.

> > > What are the consequences of the spurious interrupt?

> There will processing of false events which is undesirable.

But what actually happens?  RTC interrupts aren't going to be high
volume, if we get the odd spurious interrupt and handle it gracefully
I'm not sure we really care.

( As I'm traveling so please ignore the mail format)
spurious interrupt we get on clearing event and event can be from any
mfd children. But since now, deferring event clear is not the approach
we can ignore about the spurious interrupt.
Now looking at the old issue of determining the RTC type (periodic or tick)
on event clearing this info (RTC type) gets lost for the register since in regmap_irq
we first clear and then process the event.