Hello,
As promised, I gave this one some over-night stress testing and I can
confirm what I said previously:
- The patch does _not_ solve the interrupt loop lockups on its own.
- The patch works well in conjunction with
http://patchwork.ozlabs.org/patch/249622/ (which in turn depends on
On Thu, 2013-06-13 at 10:16 +0200, Christian Ruppert wrote:
As promised, I gave this one some over-night stress testing and I can
confirm what I said previously:
- The patch does _not_ solve the interrupt loop lockups on its own.
So, it just means my assumptions about what is happening
On Thu, Jun 13, 2013 at 11:33:56AM +0300, Andy Shevchenko wrote:
On Thu, 2013-06-13 at 10:16 +0200, Christian Ruppert wrote:
As promised, I gave this one some over-night stress testing and I can
confirm what I said previously:
- The patch does _not_ solve the interrupt loop lockups on
On Wed, Jun 12, 2013 at 3:20 PM, Grant Likely grant.lik...@linaro.org wrote:
On Fri, 7 Jun 2013 23:32:42 +0200, Wolfram Sang w...@the-dreams.de wrote:
I guess your solution is the least intrusive one. Still, it could happen
that of_match_table is scanned three times (by driver core, i2c layer,
On OLPC XO-1.75 (MMP2), a WARN_ON() was occurring during boot
since the clock being enabled by i2c-pxa had not been prepared.
Use clk_prepare_enable() to ensure that the prepare operation
has taken place.
Signed-off-by: Daniel Drake d...@laptop.org
---
drivers/i2c/busses/i2c-pxa.c | 2 +-
1
