| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
Bug: 23751002
Change-Id: I78edd202ffc74353ae9703f374a7badac0cf3084
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
Bug: 22388460
Change-Id: Ib45d9cd36725c7cb9b82540cf395bd21f5d35fd4
|
| |
|
|
| |
Change-Id: I6eadb0b5db6b3424ea2a96dd87ff2fb27e04abc2
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Change-Id: If201ba51119412f113734caf383c35884fd2fcd6
|
| |\
| |
| |
| |
| | |
* commit '3c6fa1114f34347d27b6b46dec1f3940bd50ed11':
Do not set timer if PROC_BTWRITE_TIMER_TIMEOUT_MS == 0
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| | |
bug 14999968
Change-Id: Idddc91e7bed23931cdd81a2a28ae96a6ee1b2a59
(cherry picked from commit 34547bfc4e9b4352de66f7e42f89bcafa58aa3ff)
|
| | |
| |
| |
| |
| | |
bug 14999968
Change-Id: Idddc91e7bed23931cdd81a2a28ae96a6ee1b2a59
|
| |/
|
|
|
|
|
|
| |
let BT sleep doesn't ignore the UPIO_DEASSERT command and
just use one node to control BT sleep.
Change-Id: I8d4f89be1b8e44c4d77b01a885bf7972dffe0cc3
Signed-off-by: Thomas.TT_Lin <Thomas.TT_Lin@htc.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bluesleep kernel module was used in Tegra3 platform to perform Bluetooth
low power wakelock and interrup control. Add new user-to-kernel interface
through proc fs nodes for Bluedroid to feed bluesleep with the HCI_DEV events
which bluesleep was monitoring on.
bug 7347413
Change-Id: I791be1042d5573e5207aa81e3d59fa418134f9fe
Conflicts:
libbt/include/vnd_manta.txt
|
| |
|
|
|
| |
Bug: 6837125
Change-Id: Ic3cc73f210e40d95b131a68244dc9e60bae80f37
|
| |
|
|
|
|
| |
This reverts commit d18044d184ebdbbdefe700ad439e1a4cead748f7
Change-Id: Ieb3f11f56c4368556b60c79c359a012fb8555a13
|
|
|
Bug: 6837125
Change-Id: I9e9d5a95463d5cd61a6e7f3b2f0a57c0b2f47e16
|