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-prev] [day] [month] [year] [list]

Message-ID: <20120125133518.GK3687@opensource.wolfsonmicro.com>
Date:	Wed, 25 Jan 2012 13:35:19 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Ashish Jangam <Ashish.Jangam@...tcummins.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: mfd regmap irq to handle some cases

On Wed, Jan 25, 2012 at 04:28:29AM +0000, Ashish Jangam wrote:

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

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