On Wed, 2012-02-01 at 13:10 +0530, Ashish Jangam wrote:
>
> > 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.
>
> That we can handle easily enough by adding a flag to the interrupt
> definition deferring the acknowledgement.
>
Can you let me know in which linux-next version this will be available so
that I can test it against the DA9052/53 RTC?
On Wed, Feb 01, 2012 at 01:25:14PM +0530, Ashish Jangam wrote:
> On Wed, 2012-02-01 at 13:10 +0530, Ashish Jangam wrote:
> > That we can handle easily enough by adding a flag to the interrupt
> > definition deferring the acknowledgement.
> Can you let me know in which linux-next version this will be available so
> that I can test it against the DA9052/53 RTC?
I've no particular plan to work on this myself - I would suggest that
you work on this if it is an urgent requirement for your device.