From: Kalle Jokiniemi <kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org>
To: Shubhrajyoti Datta
<omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kalle.jokiniemi-ieSKYCWCyXoAvxtiuMwx3w@public.gmane.org,
"Strashko,
Grygorii" <grygorii.strashko-l0cyMroinI0@public.gmane.org>,
Kevin Hilman
<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
<w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org"
<ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
"tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org"
<tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Datta, Shubhrajyoti" <shubhrajyoti-l0cyMroinI0@public.gmane.org>,
"Kankroliwala, Huzefa" <huzefank-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v3] ARM: OMAP: i2c: fix interrupt flood during resume
Date: Mon, 15 Oct 2012 17:10:23 +0300 [thread overview]
Message-ID: <1350310223.2014.10.camel@kj-X230> (raw)
In-Reply-To: <CAM=Q2cuJ-0VSgkBme_Cg8YD2cBG5NZcO6aBeTsPZ_PQGMwJ=bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
ma, 2012-10-15 kello 15:41 +0530, Shubhrajyoti Datta kirjoitti:
> On Mon, Oct 15, 2012 at 2:46 PM, Kalle Jokiniemi
> <kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org> wrote:
> > ma, 2012-10-15 kello 09:21 +0300, Kalle Jokiniemi kirjoitti:
> >> Hi,
> >>
> >> pe, 2012-10-12 kello 14:46 +0000, Strashko, Grygorii kirjoitti:
> >> > Hi Kevin,
> >> >
> >> > yep, [1] is the same fix - thanks.
> >> >
> >> > Hi Kalle,
> >> >
> >> > i've applied these changes and PM runtime fix on top of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git (omap2plus_defconfig)
> >> > Could you check it with your use case, pls? (just to be sure that idea is right)
> >>
> >> Odd, it's not working. I'll add some debug prints to see what happens
> >> there.
> >
> > Well, seems after enabling irq 23 in the resume_noirq, someone does
> > i2c_xfer and there is consequent flood of i2c_xfers and interrupts.
> If there is continuous xfers, you could enable debug LL and see who is
> queuing the
> transfers.
>
> >
> > Not sure now how these IRQ numbers get mapped these days, my debug print
> > says it's irq number 72 (UART1 from TRM) that is flooding (although it's
> > printed from the i2c-omap isr function, so it's still I2C bus irq...).
>
> Can you do a cat /proc/interrupts
Yes :)
[root@localhost proc]# cat
interrupts
CPU0
20: 0 INTC gpmc
23: 2 INTC TWL4030-PIH
25: 0 INTC l3-debug-irq
26: 0 INTC l3-app-irq
28: 48157 INTC DMA
40: 0 INTC omap-iommu.0
52: 0 INTC dsp_wdt
53: 807807 INTC gp_timer
65: 0 INTC omap-sham
72: 5490 INTC omap_i2c
73: 85 INTC omap_i2c
77: 0 INTC omap_i2c
90: 1069 INTC OMAP UART2
102: 55940 INTC mmc0
179: 6142 GPIO omap2-onenand
306: 44666 PRCM pm_wkup
315: 4 PRCM hwmod_io, pm_io
338: 0 twl4030 twl4030_gpio
343: 2 twl4030 twl4030_power
346: 0 twl4030 twl4030_pwrbutton
348: 2 twl4030 twl4030_usb
349: 0 twl4030 rtc0
Hmm, I did not notice that PIH handler before, makes sense now that it
triggers the flood (irq 23) as it is really the one that passes the
interrupts to other handlers.
- Kalle
>
>
> >
> > The irq enabling (in resume_noirq) is still slightly progressing after
> > the flooding starts, but my watchdog kicks in before we get to the
> > finish.
> >
> > Attached my debug prints patch and log. I used also "no_console_suspend"
> > boot option.
> >
> > - Kalle
> >
next prev parent reply other threads:[~2012-10-15 14:10 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 [this message]
2012-10-17 16:02 ` Felipe Balbi
[not found] ` <20121017160200.GA6567-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-10-18 6:51 ` Kalle Jokiniemi
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=1350310223.2014.10.camel@kj-X230 \
--to=kalle.jokiniemi-4y2fmlu5ms8onnqtyk5kxq@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
--cc=huzefank-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=omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@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).