[PATCH] fix-lis302dl-isr-lock.patch

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Andy Green wrote:
|> The ISR clears the interrupt source, what can happen until that is done
|> that makes everything slow?
|
| I was thinking of the interrupt getting asserted all the time until
| the (slow) acknowledgement has been sent.

... but how does that make the problem?  No ISR would ever execute if
somehow the not-yet-ack'd interrupt source kept recursing... like Joerg
said it would blow up.  Maybe it was something else subtle in the code
but I ended up feeling I was seeing the same issue more than once.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkfyrJoACgkQOjLpvpq7dMoHEgCgkd8DLpqLPLg3z2l1nhOoAJ9b
0EAAmgJp1KWr8KQ6i5KuP/TU1Uj3ynJ4
=alE9
-----END PGP SIGNATURE-----