-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| - set_irq_handler(irqno, handle_edge_irq); | + //set_irq_handler(irqno, handle_edge_irq); | + set_irq_handler(irqno, handle_level_irq); | When the system resumed, it is looped in handling low level IRQ, | which is what I mentioned before, "the IRQ strom". | | Any thoughts? Normally I would say we just need to take your patches and move on even if they were on our local tree only, since it solves a problem. But if I understood it they only solve this storm issue specifically around the wake action... I am not sure at all that the stuff we see around level IRQ (also it seems to stun the device sometimes through motion sensors level on stable branch) is not a general problem some or all of the time outside of wake too. It feels like we have all this time (I saw this storm behaviour using level back in early part of the year) either been missing a trick somewhere about using level or it's broken somehow. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkigR0ACgkQOjLpvpq7dMrbgQCfb35DWUveY8DNgax0zuXAcEWd AN4AnR5CmT8uyUYwQ5BPf+5TsWUvr7ae =sS9A -----END PGP SIGNATURE-----
