summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCheng-Yi Chiang <cychiang@chromium.org>2016-12-13 22:49:28 +0800
committerchrome-bot <chrome-bot@chromium.org>2016-12-16 04:51:21 -0800
commite4cfb42dc25e5196bc0115c1402db24359adfe8b (patch)
treea3ab5f2da6caefa9ec3062bba754b7fab71d77fd
parent52aaabb2f52448b55574fed2b40aae0ae96d648e (diff)
downloadadhd-e4cfb42dc25e5196bc0115c1402db24359adfe8b.tar.gz
CRAS: alsa_io - Set severe underrun threshold to five seconds
As explained in the issue, severe underrun is only targeted for special case where bad dma driver makes hw_ptr jumps by a large distance and creates a severe underrun that can not be recovered by filling blocks of zeros. It should not be easily triggered by normal underrun or stressing system. BUG=chrome-os-partner:60497, chromium:662786 TEST=run balloon test in issue 60497, should not see resetting device. Change-Id: I78d13d428cf11b06dbec05454340abc376f2290e Reviewed-on: https://chromium-review.googlesource.com/418566 Commit-Ready: Cheng-Yi Chiang <cychiang@chromium.org> Tested-by: Cheng-Yi Chiang <cychiang@chromium.org> Reviewed-by: Cheng-Yi Chiang <cychiang@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
-rw-r--r--cras/src/server/cras_alsa_io.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/cras/src/server/cras_alsa_io.c b/cras/src/server/cras_alsa_io.c
index 9d8f4609..59456ef7 100644
--- a/cras/src/server/cras_alsa_io.c
+++ b/cras/src/server/cras_alsa_io.c
@@ -57,7 +57,7 @@
* (avail - buffer_size) is greater than SEVERE_UNDERRUN_MS * rate,
* it is a severe underrun. Main thread should disable and then enable
* device to recover it from underrun. */
-#define SEVERE_UNDERRUN_MS 20
+#define SEVERE_UNDERRUN_MS 5000
/* This extends cras_ionode to include alsa-specific information.
* Members: