android_hardware_broadcom_libbt/src/upio.c, branch cm-13.0 Unnamed repository; edit this file 'description' to name the repository. Avoid frequently operation on btwrite 2015-09-22T18:23:21+00:00 zhaoyang yin yinzhaoyang@huawei.com 2015-09-20T16:38:43+00:00 9ac18e70df13c2723ad9a8e7460ba0129fda7a03 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: 24201064 Change-Id: I3aec20bc52552f9181ccd1a257f1a04492999a68 
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: 24201064
Change-Id: I3aec20bc52552f9181ccd1a257f1a04492999a68
Revert upio changes to fix wear timeouts. 2015-09-03T05:30:47+00:00 tturney tturney@google.com 2015-09-03T05:27:03+00:00 00f5e91d255b35230051b14810ae201090e8d7b1 Bug: 23751002 Change-Id: I78edd202ffc74353ae9703f374a7badac0cf3084 
Bug: 23751002
Change-Id: I78edd202ffc74353ae9703f374a7badac0cf3084
Fix btwrite timer timeout for Angler (1/2) 2015-08-31T22:41:47+00:00 tturney tturney@google.com 2015-08-19T17:38:28+00:00 b7b7af83922fc5918d2632402daa3824364806fb 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 
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
Remove the optimization for unarming the timer 2015-07-29T18:18:43+00:00 tturney tturney@google.com 2015-07-29T00:32:50+00:00 955f8769d470fb2bbb8a1d44a39ce8e104085d9a Bug: 22388460 Change-Id: Ib45d9cd36725c7cb9b82540cf395bd21f5d35fd4 
Bug: 22388460
Change-Id: Ib45d9cd36725c7cb9b82540cf395bd21f5d35fd4
Fix Fugu LPM compile error 2015-06-01T22:57:00+00:00 Andre Eisenbach eisenbach@google.com 2015-06-01T22:57:00+00:00 f9751ef9958af460a4bbdc2f73dba8f6b232ed60 Change-Id: I6eadb0b5db6b3424ea2a96dd87ff2fb27e04abc2 
Change-Id: I6eadb0b5db6b3424ea2a96dd87ff2fb27e04abc2
Fix for bluedroid sometimes holding kernel wake lock inadvertendly 2015-06-01T17:57:17+00:00 Prerepa Viswanadham dham@google.com 2015-05-28T22:41:19+00:00 552a6ef12d4661234f3be5e8a47954b4b634560e Two problems - sometimes bluedroid will not issue upio_set to release kernel wake lock. Timeout would fire but would not release lpm driver cmd to release kernel wake lock - lpm wake lock was not being extended as bluedroid would constantly use the interface. Bug: 21063567 Change-Id: I898508493bbf7b8c2ddb79d7c7398b6900ade12c 
Two problems
- sometimes bluedroid will not issue upio_set to release kernel
wake lock. Timeout would fire but would not release lpm driver
cmd to release kernel wake lock
- lpm wake lock was not being extended as bluedroid would
constantly use the interface.

Bug: 21063567
Change-Id: I898508493bbf7b8c2ddb79d7c7398b6900ade12c
Add missing includes. 2015-01-30T06:20:56+00:00 Elliott Hughes enh@google.com 2015-01-30T06:20:56+00:00 ad6bbbd04daa376c541deba75c72d04fea443de1 Change-Id: If201ba51119412f113734caf383c35884fd2fcd6 
Change-Id: If201ba51119412f113734caf383c35884fd2fcd6
am 3c6fa111: am 822e4da8: Do not set timer if PROC_BTWRITE_TIMER_TIMEOUT_MS == 0 2014-08-26T22:45:56+00:00 Devin Kim dojip.kim@lge.com 2014-08-26T22:45:56+00:00 21371a06c8ab730b56276e7dc6aa768c59e13db3 * commit '3c6fa1114f34347d27b6b46dec1f3940bd50ed11': Do not set timer if PROC_BTWRITE_TIMER_TIMEOUT_MS == 0 
* commit '3c6fa1114f34347d27b6b46dec1f3940bd50ed11':
  Do not set timer if PROC_BTWRITE_TIMER_TIMEOUT_MS == 0
Do not set timer if PROC_BTWRITE_TIMER_TIMEOUT_MS == 0 2014-08-25T22:54:10+00:00 Devin Kim dojip.kim@lge.com 2014-08-23T06:33:34+00:00 822e4da8a67b777df7fa40b00aba434cb94ff601 When PROC_BTWRITE_TIMER_TIMEOUT_MS is set to 0, it disables btwrite timer setup so that bluesleep driver controls timeout for tx data Bug: 16889688 Change-Id: I721ae88fdd671495c509acfcbdee559daf34e089 
When PROC_BTWRITE_TIMER_TIMEOUT_MS is set to 0, it disables btwrite timer setup
so that bluesleep driver controls timeout for tx data

Bug: 16889688
Change-Id: I721ae88fdd671495c509acfcbdee559daf34e089
Fix ms to ns conversion unit 2014-05-16T22:36:52+00:00 Matthew Xie mattx@google.com 2014-05-16T22:10:40+00:00 3218eaffc110ffcace3ae05d37466c6dcc3c86f0 bug 14999968 Change-Id: Idddc91e7bed23931cdd81a2a28ae96a6ee1b2a59 (cherry picked from commit 34547bfc4e9b4352de66f7e42f89bcafa58aa3ff) 
bug 14999968
Change-Id: Idddc91e7bed23931cdd81a2a28ae96a6ee1b2a59
(cherry picked from commit 34547bfc4e9b4352de66f7e42f89bcafa58aa3ff)