public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: ext-Eero.Nurkkala@nokia.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP: GPIO: Avoid generating extra IRQs
Date: Wed, 5 Aug 2009 18:15:41 +0300	[thread overview]
Message-ID: <20090805151540.GU7374@atomide.com> (raw)
In-Reply-To: <1FFEF31EBAA4F64B80D33027D4297760047F6AECFD@NOK-EUMSG-02.mgdnok.nokia.com>

* ext-Eero.Nurkkala@nokia.com <ext-Eero.Nurkkala@nokia.com> [090805 17:45]:
> 
> >>               l ^= bank->saved_datain;
> >>               l &= bank->non_wakeup_gpios;
> >> -             if (l) {
> >> +
> >> +             /*
> >> +              * No need to generate IRQs for the rising edge for gpio IRQs
> >> +              * configured with falling edge only; and vice versa.
> >> +              */
> >> +             gen0 = l & bank->saved_fallingdetect;
> >> +             gen0 &= bank->saved_datain;
> >> +
> >> +             gen1 = l & bank->saved_risingdetect;
> >> +             gen1 &= ~(bank->saved_datain);
> >> +
> 
> > Is the gen0 &= correct or should it also clear the bits?
> 
> What do you mean, eg, what bits should be cleared?
> 
> gen0 = (bit has changed) and is falling_edge
> gen0 &= (the bit has changed) is falling edge and former state was "HIGH"
> (transition from HIGH to LOW has occurred)
> 
> for rising edge, needed is LOW to HIGH transition.

OK, my comment was just based on looking at the patch, sounds like
you have verified that it's correct. 

Tony

  reply	other threads:[~2009-08-05 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  6:26 [PATCH] OMAP: GPIO: Avoid generating extra IRQs ext-eero.nurkkala
2009-08-05 13:17 ` Tony Lindgren
2009-08-05 14:41   ` ext-Eero.Nurkkala
2009-08-05 15:15     ` Tony Lindgren [this message]
2009-08-05 17:56   ` ext-Eero.Nurkkala
2009-08-10 16:10 ` [APPLIED] " Tony Lindgren

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=20090805151540.GU7374@atomide.com \
    --to=tony@atomide.com \
    --cc=ext-Eero.Nurkkala@nokia.com \
    --cc=linux-omap@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