From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <Ashish.Jangam@kpitcummins.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mfd regmap irq to handle some cases
Date: Wed, 25 Jan 2012 13:35:19 +0000 [thread overview]
Message-ID: <20120125133518.GK3687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <C3AE124F08223B42BC95AEB82F0F6CED1FDCFDBC@KCHJEXMB01.kpit.com>
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.
next prev parent reply other threads:[~2012-01-25 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1FDCFCAF@KCHJEXMB01.kpit.com>
2012-01-23 13:33 ` mfd regmap irq to handle some cases Ashish Jangam
2012-01-23 15:18 ` Mark Brown
2012-01-25 4:28 ` Ashish Jangam
2012-01-25 13:35 ` Mark Brown [this message]
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1FDDA3C3@KCHJEXMB02.kpit.com>
2012-02-01 7:55 ` Ashish Jangam
2012-02-01 9:46 ` Mark Brown
2012-01-23 8:47 Ashish Jangam
2012-01-23 11:52 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120125133518.GK3687@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Ashish.Jangam@kpitcummins.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.