public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ashish Jangam <ashish.jangam@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: mfd regmap irq to handle some cases
Date: Mon, 23 Jan 2012 14:17:03 +0530	[thread overview]
Message-ID: <1327308423.23929.8.camel@dhruva> (raw)

Hi Mark,

DA9052-53 PMIC supports Tick & Periodic Alarm. On expiry of Alarm an event gets generate
and data ( about the alram type - Tick or Periodic) also gets lock in a register. This
data needs to be read from the register before event is cleared . But since in regmap irq
events are cleared first and then left for processing (which is the obvious way to do) but
in this approach data gets loss from the DA9052-53 register and alarm type cannot be
determined.

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

Regards,
Ashish



             reply	other threads:[~2012-01-23  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23  8:47 Ashish Jangam [this message]
2012-01-23 11:52 ` 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
     [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=1327308423.23929.8.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