diff options
| author | tturney <tturney@google.com> | 2015-08-19 10:38:28 -0700 |
|---|---|---|
| committer | tturney <tturney@google.com> | 2015-08-31 15:41:47 -0700 |
| commit | b7b7af83922fc5918d2632402daa3824364806fb (patch) | |
| tree | ccfa5677a63a0ec066272d5eab655416af0eb262 /include | |
| parent | 955f8769d470fb2bbb8a1d44a39ce8e104085d9a (diff) | |
| download | android_hardware_broadcom_libbt-b7b7af83922fc5918d2632402daa3824364806fb.tar.gz android_hardware_broadcom_libbt-b7b7af83922fc5918d2632402daa3824364806fb.tar.bz2 android_hardware_broadcom_libbt-b7b7af83922fc5918d2632402daa3824364806fb.zip | |
Fix btwrite timer timeout for Angler (1/2)
1. For vnd_angler.txt:
Set PROC_BTWRITE_TIMER_TIMEOUT_MS to 0
to avoid upio start and stop timer when LMP
is enabled and BT_WAKE is asserted and
de-asserted. This time is useless and would
set btwrite to 0 by mistake even when host
is sending data to UART, and this would
de-assert BT_WAKE by mistake.
2. For hardware.c:
For chipset 4358 we need to set LPM_HC_IDLE_THRESHOLD
to 24, so we need to reduce the multiplier
to make timeout_ms a reasonable value. Without
modification, the timeout_ms would be 36000ms
which is too large.
3. For upio.c:
Need to set lmp_proc_cb.btwrite_active even though
PROC_BTWRITE_TIMER_TIMEOUT_MS is set to 0.
Otherwise, btwrite would be written very frequently.
Bug: 23248798
Change-Id: Ie55c346785679e51a771d5e46270c0858e6082ee
Diffstat (limited to 'include')
| -rwxr-xr-x | include/vnd_angler.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/vnd_angler.txt b/include/vnd_angler.txt index 103b656..8d7b271 100755 --- a/include/vnd_angler.txt +++ b/include/vnd_angler.txt @@ -2,7 +2,7 @@ BLUETOOTH_UART_DEVICE_PORT = "/dev/ttyHS0" FW_PATCHFILE_LOCATION = "/vendor/firmware/" BT_WAKE_VIA_PROC = TRUE BT_WAKE_VIA_PROC_NOTIFY_DEASSERT=TRUE -PROC_BTWRITE_TIMER_TIMEOUT_MS = 4000 +PROC_BTWRITE_TIMER_TIMEOUT_MS = 0 UART_TARGET_BAUD_RATE = 3000000 LPM_IDLE_TIMEOUT_MULTIPLE = 5 LPM_HC_IDLE_THRESHOLD = 24 |