According to the ALSA documentation, snd_pcm_readi() returns -ESTRPIPE
when a suspend event occured. But xrun_recovery() checks for -EAGAIN
instead.

If the ALSA client is connected to the ALSA loopback device, it leads to
an infinite loop in the client when the computer is resumed from sleep.
The client takes up to 99% of the CPU resources.

The problem is fixed by a proper error checking of snd_pcm_readi().

A word of caution however: on kernels prior to 3.8, it will trigger a
bug in the snd-aloop driver, and may lead to a kernel oops.
The kernel fix can be found there:
http://www.spinics.net/lists/stable-commits/msg23379.html

Signed-off-by: elboulangero <elboulangero@gmail.com>

Patch provided by colinf in

   http://trac.jackaudio.org/attachment/ticket/227/typos.patch

alsa_in/alsa_out need to close the ALSA device they use when freewheeling starts and then reopen it, along with reset resampling parameters, when it ends. this avoids bizarre behaviour during freewheeling as they try to do audio i/o with a still open PCM device

memops.h has been moved from the public jack headers residing in jack/
to include/.