Re: [PATCH 0/2] I2C: OMAP: spurious IRQ fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 27 Apr 2009, Aaro Koskinen wrote:

> Paul Walmsley wrote:
> > It seems to work: under constant I2C load, no spurious IRQ messages
> > showed up after several hours of testing.  (Without these patches,
> > spurious IRQs usually show up in a few minutes.)  Some of the code has
> > also been cleaned up.
> > 
> > Any feedback on how this series works for others is appreciated.
> > 
> > Tested on N800, Beagle and 3430SDP.
> 
> With these patches I'm getting receive overruns quite easily on rx51 when
> doing large reads from TWL4030 RTC.

A brief update for anyone following along on the list: 

Aaro sent me a test-case.  It seems that the receive overruns only affect 
PM kernels.  They are caused by the MPU going to sleep while it waits for 
an I2C interrupt.  It turns out that the current driver causes receive 
overruns also; it just hides them.  The receive overruns are fairly 
straightforward to deal with by setting an MPU wakeup latency constraint 
during I2C operations.

So the plan now is to send two sets of patches.  One set will resolve the 
spurious IRQ problems.  The other will resolve the receive overrun 
issues and will be mostly against the PM branch.


- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux