From: Ashish Jangam <ashish.jangam@kpitcummins.com>
To: <broonie@opensource.wolfsonmicro.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: mfd regmap irq to handle some cases
Date: Wed, 1 Feb 2012 13:25:14 +0530 [thread overview]
Message-ID: <1328082914.19234.3.camel@dhruva> (raw)
In-Reply-To: <C3AE124F08223B42BC95AEB82F0F6CED1FDDA3C3@KCHJEXMB02.kpit.com>
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?
next parent reply other threads:[~2012-02-01 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1FDDA3C3@KCHJEXMB02.kpit.com>
2012-02-01 7:55 ` Ashish Jangam [this message]
2012-02-01 9:46 ` mfd regmap irq to handle some cases Mark Brown
[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
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=1328082914.19234.3.camel@dhruva \
--to=ashish.jangam@kpitcummins.com \
--cc=broonie@opensource.wolfsonmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).