On 08/14/2013 03:23 AM, Felipe Balbi wrote:
Hi,
On Mon, Aug 12, 2013 at 09:43:24AM +0800, Qiao Zhou wrote:
On 08/02/2013 03:31 PM, Felipe Balbi wrote:
Hi,
On Fri, Aug 02, 2013 at 01:15:33PM +0800, Qiao Zhou wrote:
On 08/01/2013 06:21 PM, Qiao Zhou wrote:
v2-v1:
stop pcm stream instead
On 08/02/2013 03:31 PM, Felipe Balbi wrote:
Hi,
On Fri, Aug 02, 2013 at 01:15:33PM +0800, Qiao Zhou wrote:
On 08/01/2013 06:21 PM, Qiao Zhou wrote:
v2-v1:
stop pcm stream instead of wake up the sleep thread, which is more
reasonable.
Qiao Zhou (1):
usb: gadget: audio file: wake up sleep
On 08/01/2013 03:33 PM, Clemens Ladisch wrote:
Qiao Zhou wrote:
when usb audio device removes, it doesn't notify the ALSA read /
write thread. due to no data transmitting any more, those threads
wait for a long timeout(10s), then detects IO error. it causes
long time blocking in upper layer
still be used after audio unbind, and
we should only set null to it in audio_pcm_close.
Signed-off-by: Qiao Zhou zhouq...@marvell.com
---
drivers/usb/gadget/f_audio_source.c | 11 +--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/f_audio_source.c
b
v2-v1:
stop pcm stream instead of wake up the sleep thread, which is more
reasonable.
Qiao Zhou (1):
usb: gadget: audio file: wake up sleep thread when device unbind
drivers/usb/gadget/f_audio_source.c | 11 +--
1 files changed, 9 insertions(+), 2 deletions(-)
--
To unsubscribe
met an issue with using ADK2012 to test usb audio. android audio
thread is blocked 10s after ADK2012 HW disconnect(unpluged). In
audio_unbind function, we should wake up and notify potential
sleep thread timely.
not sure it's a good solution. please help suggest if any. thanks.
Qiao Zhou (1
if necessary
when audio unbind. substream pcm may still be used after audio
unbind, and we should only set null to it in audio_pcm_close.
Signed-off-by: Qiao Zhou zhouq...@marvell.com
---
drivers/usb/gadget/f_audio_source.c | 12 ++--
1 files changed, 10 insertions(+), 2 deletions(-)
diff
