linux-kernel - Re: mfd regmap irq to handle some cases

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1328082914.19234.3.camel@dhruva>
Date:	Wed, 1 Feb 2012 13:25:14 +0530
From:	Ashish Jangam <ashish.jangam@...tcummins.com>
To:	<broonie@...nsource.wolfsonmicro.com>
CC:	<linux-kernel@...r.kernel.org>
Subject: Re: mfd regmap irq to handle some cases

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?


--
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/