From: Kalle Jokiniemi <kalle.jokiniemi-4y2FMlU5MS8onNqTyK5kxQ@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: kalle.jokiniemi-ieSKYCWCyXoAvxtiuMwx3w@public.gmane.org,
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
Kevin Hilman
<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
Shubhrajyoti Datta
<omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Grygorii Strashko
<grygorii.strashko-l0cyMroinI0@public.gmane.org>,
Shubhrajyoti Datta <shubhrajyoti-l0cyMroinI0@public.gmane.org>,
Huzefa Kankroliwala <huzefank-l0cyMroinI0@public.gmane.org>,
Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH] i2c: omap: fix spurious IRQs: disable/enable IRQ at INTC when idle
Date: Fri, 02 Nov 2012 08:17:57 +0200 [thread overview]
Message-ID: <1351837077.16513.24.camel@kj-X230> (raw)
In-Reply-To: <20121101224921.GE22956-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
to, 2012-11-01 kello 23:49 +0100, Wolfram Sang kirjoitti:
> Hi,
>
> > Anyway new patch coming soon :)
>
> Was there one? I have skimmed a number of threads discussing spurious
> interrupts or interrupt floods but AFAICS all discussions ended up in
> trying another approach later or fixing the issue somewhere else than
> I2C. Is this correct? Or is there a bugfix patch left for 3.7 that I
> missed?
The problem was not actually in the i2c driver itself, the twl4030
Primary/Secondary interrupt handler irq wake up order was the problem.
The fix was this:
https://patchwork.kernel.org/patch/1601271/
Actually, Samuel, did you pick up my patch? I never got any response
after Kevin acked it.
- Kalle
>
> Thanks,
>
> Wolfram
>
prev parent reply other threads:[~2012-11-02 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 18:40 [PATCH] i2c: omap: fix spurious IRQs: disable/enable IRQ at INTC when idle Kevin Hilman
[not found] ` <1350067225-24589-1-git-send-email-khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-12 19:30 ` Shubhrajyoti Datta
2012-10-15 6:25 ` Kalle Jokiniemi
2012-10-15 17:31 ` Kevin Hilman
[not found] ` <87zk3ntzfe.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2012-10-16 1:02 ` Tony Lindgren
[not found] ` <20121016010223.GL15569-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-10-16 8:47 ` Kalle Jokiniemi
2012-11-01 22:49 ` Wolfram Sang
[not found] ` <20121101224921.GE22956-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-11-02 6:17 ` Kalle Jokiniemi [this message]
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=1351837077.16513.24.camel@kj-X230 \
--to=kalle.jokiniemi-4y2fmlu5ms8onnqtyk5kxq@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=nm-l0cyMroinI0@public.gmane.org \
--cc=omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@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).