linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Jokiniemi <kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org>
To: balbi-l0cyMroinI0@public.gmane.org
Cc: Kevin Hilman
	<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	grygorii.strashko-l0cyMroinI0@public.gmane.org,
	shubhrajyoti-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH v3] ARM: OMAP: i2c: fix interrupt flood during resume
Date: Thu, 18 Oct 2012 09:51:13 +0300	[thread overview]
Message-ID: <1350543073.2014.35.camel@kj-X230> (raw)
In-Reply-To: <20121017160200.GA6567-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>

ke, 2012-10-17 kello 19:02 +0300, Felipe Balbi kirjoitti:
> Hi,
> 
> On Thu, Oct 11, 2012 at 02:08:25PM -0700, Kevin Hilman wrote:
> > Hi Kalle,
> > 
> > Kalle Jokiniemi <kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org> writes:
> > 
> > > The resume_noirq enables interrupts one-by-one starting from
> > > first one. Now if the wake up event for suspend came from i2c
> > > device, the i2c bus irq gets enabled before the threaded
> > > i2c device irq, causing a flood of i2c bus interrupts as the
> > > threaded irq that should clear the event is not enabled yet.
> > >
> > > Fixed the issue by adding suspend_noirq and resume_early
> > > functions that keep i2c bus interrupts disabled until
> > > resume_noirq has run completely.
> > >
> > > Issue was detected doing a wake up from autosleep with
> > > twl4030 power key on N9. Patch tested on N9.
> > >
> > > Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org>
> > 
> > This version looks good, thanks for the extra comments.
> > 
> > Reviewed-by: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
> > Tested-by: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
> > 
> > Wolfram, This should also probably be Cc'd to stable since it affects
> > earlier kernels as well.  Thanks,
> 
> just to make sure we're not fixing the wrong problem... does [1] help in
> any way ?

Yes, I was fixing the wrong problem, this patch is obsolete. But the
problem was in the TWL interrupt handling (PIH was run before SIH), not
in i2c. See my other patch "twl4030: Fix chained irq handling on resume
from suspend"

> 
> [1] http://marc.info/?l=linux-omap&m=135048839915719&w=2
> 

Could be related, though if I understood correctly, that runtime pm
stuff gets run at noirq phase, so it probably does not help.

- Kalle

  parent reply	other threads:[~2012-10-18  6:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 12:18 [PATCH v3] ARM: OMAP: i2c: fix interrupt flood during resume Kalle Jokiniemi
     [not found] ` <1349871480-25182-1-git-send-email-kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org>
2012-10-11  7:59   ` Shubhrajyoti Datta
2012-10-11 21:08   ` Kevin Hilman
     [not found]     ` <87ipag90om.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-12 10:18       ` Strashko, Grygorii
2012-10-12 11:33         ` Shubhrajyoti
     [not found]           ` <5077FFEC.5040407-l0cyMroinI0@public.gmane.org>
2012-10-12 12:55             ` Kankroliwala, Huzefa
2012-10-12 13:28         ` Kalle Jokiniemi
     [not found]         ` <902E09E6452B0E43903E4F2D568737AB2C87B0-bXo5r3zvlxeIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-10-12 14:17           ` Kevin Hilman
2012-10-12 14:34         ` Kevin Hilman
     [not found]           ` <87d30n7o9q.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-12 14:46             ` Strashko, Grygorii
2012-10-12 16:43               ` Kevin Hilman
     [not found]                 ` <87r4p363ps.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-12 18:11                   ` Shubhrajyoti Datta
2012-10-12 19:04                     ` Kevin Hilman
     [not found]                       ` <87txtzy0jf.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-12 19:15                         ` shubhro
     [not found]               ` <902E09E6452B0E43903E4F2D568737AB2C8C9F-bXo5r3zvlxeIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-10-15  6:21                 ` Kalle Jokiniemi
2012-10-15  9:16                   ` Kalle Jokiniemi
2012-10-15 10:11                     ` Shubhrajyoti Datta
     [not found]                       ` <CAM=Q2cuJ-0VSgkBme_Cg8YD2cBG5NZcO6aBeTsPZ_PQGMwJ=bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-15 14:10                         ` Kalle Jokiniemi
2012-10-17 16:02       ` Felipe Balbi
     [not found]         ` <20121017160200.GA6567-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-10-18  6:51           ` Kalle Jokiniemi [this message]
2012-10-18  7:11             ` Felipe Balbi

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=1350543073.2014.35.camel@kj-X230 \
    --to=kalle.jokiniemi-4y2fmlu5ms8onnqtyk5kxq@public.gmane.org \
    --cc=balbi-l0cyMroinI0@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
    --cc=kalle.jokiniemi-ieSKYCWCyXoAvxtiuMwx3w@public.gmane.org \
    --cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shubhrajyoti-l0cyMroinI0@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).