From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <ashish.jangam@kpitcummins.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mfd regmap irq to handle some cases
Date: Mon, 23 Jan 2012 11:52:25 +0000 [thread overview]
Message-ID: <20120123115225.GB29465@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327308423.23929.8.camel@dhruva>
On Mon, Jan 23, 2012 at 02:17:03PM +0530, Ashish Jangam wrote:
Please fix your mailer to word wrap within 80 columns. I've reflowed
your text for legibility.
> For a quick fix in regmap irq we may tempt to defer event
> clarification after processing of event but there is a problem in this
That's not going to work in general, it means there's a race between
handling the interrupt and acknowledging the interrupt which leads to
interrupts being dropped if you get a new interrupt before the ack has
been written back.
> 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?
next prev parent reply other threads:[~2012-01-23 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 8:47 mfd regmap irq to handle some cases Ashish Jangam
2012-01-23 11:52 ` Mark Brown [this message]
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1FDCFCAF@KCHJEXMB01.kpit.com>
2012-01-23 13:33 ` Ashish Jangam
2012-01-23 15:18 ` Mark Brown
2012-01-25 4:28 ` Ashish Jangam
2012-01-25 13:35 ` Mark Brown
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1FDDA3C3@KCHJEXMB02.kpit.com>
2012-02-01 7:55 ` Ashish Jangam
2012-02-01 9:46 ` 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=20120123115225.GB29465@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.