| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| |
| | |
https://android.googlesource.com/platform/hardware/broadcom/libbt into cm-13.0
Android 6.0.1 release 22
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
1, enable SCO_USE_I2S_INTERFACE for sturgeon
2, configure audio configuration in hw_sco_config for I2S as SCO_CODEC_CVSD by default
BUG=24044548
Change-Id: Id39102ee812eb2b173dfab45f4fb97fd99c5e7b8
Signed-off-by: z00184990 <z00184990@notesmail.huawei.com>
|
| | |\
| | |
| | |
| | |
| | | |
* commit 'b7b7af83922fc5918d2632402daa3824364806fb':
Fix btwrite timer timeout for Angler (1/2)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
BCM4343 doesn't have the name starting with 'BCM'. So fix the name
to use the dynamic FW loading for BCM4343
Bug: 21268506
Change-Id: Id43a748bf6180c2464671d35e7be3caaa6532e82
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: Ifca9393c8e7499c547c6080366f8a92901625f3f
(cherry picked from commit d0b5eb6c7206da275e6cae8587dcd3a19e48b786)
|
| |\ \ \
| | |/
| |/|
| | | |
Android 6.0.0 release 26
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| | |
Change-Id: If31e05cd4789660780b4f34288c0d4023554afe6
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is totally broken. If the chipset is bcm4530 then it added e.g.
_wisol to it and looked for bcm4530_wisol.hcd. The firmware files are
named e.g. bcm4350_V0301.0636_wisol.hcd. What we need to do if a special
flavor is needed to search for the string in the name of the file we are
currently inspecting.
Change-Id: If804de56064cf8993a32af98c7ec39126ebd349a
|
| | |
| |
| |
| | |
Change-Id: I6dd13c7ec087cf536b1fbbfe6325ec93b153d7ae
|
| | |
| |
| |
| | |
Change-Id: I92864265dde328d749fa4745d4955e6864c1438d
|
| | |
| |
| |
| |
| |
| | |
Based on codeworkx's patches for brcm_patchram.
Change-Id: Ifefa4f2b98b9186695677dc6f02fcbb63b32e3b7
|
| | |
| |
| |
| |
| |
| |
| | |
* This improves reliability on chips such as BCM4335.
* Also externalize some configuration.
Change-Id: I1271f0c1c3e602c8bfe9f816f57c9cb6add04b3a
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* We need to apply an initial patch to the BCM4335 hardware to prevent
chip crashes, so add support for a prepatch designated by
FW_PRE_PATCH.
Change-Id: I2d2ec59094a1ae2cb39e1f41d4853ac4a45d1902
|
| |/
|
|
|
|
|
|
|
|
| |
* Concurrent WiFi/BT firmware loading can cause a chip crash.
* Kernel supports a btlock device which is a simple semaphore that can
protect from this situation.
* Add support in the Bluedroid vendor lib for this on the BT side, as
WiFi is already done directly in the kernel.
Change-Id: I8b9d3b1ccd06cc5d5528c7d6d685048c258d9887
|
| |\ |
|
| | |
| |
| |
| | |
Change-Id: I858df6e7d5361cc6f9bbb7b24c40639714455c5d
|
| |/
|
|
| |
Change-Id: If201ba51119412f113734caf383c35884fd2fcd6
|
| |\
| |
| |
| |
| | |
* commit '1798e093fd12c3aaa2d68600098d4dbf16c8f571':
libbt-vendor : Modified hardware config sequence
|
| | |
| |
| |
| |
| |
| |
| | |
Update uart baud rate to 3M after HCI reset. CSP:832610
Change-Id: I568cd6a1ea2601bcd0ac6cba6bf4208900698f86
Signed-off-by: Malayasen Rout <mrout@broadcom.com>
|
| |\|
| |
| |
| |
| |
| |
| | |
200ms" into klp-modular-dev
* commit '5a63d16f5220c1706f866225a10ea9aa7bd898bc':
BT: Increasing firmware settlement delay to 200ms
|
| | |
| |
| |
| |
| | |
Change-Id: I61f176ad82184e0e46b99844e2f26ccba49614ec
Signed-off-by: Alok Moondra <alokm@broadcom.com>
|
| |/
|
|
|
|
| |
Bug 13764086
Change-Id: I38d344942096b09aa29eeff7398f1e6890d48d6b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A pair of asynchronous call-in and call-back API are added into the Host
Controller Vendor Lib interface (bt_vendor_lib.h). The caller calls this new
call-in function to inform the vendor module to perform vendor-specific
shutdown process (e.g. send HCI_RESET to BT Controller) before the caller calls
for interface cleanup() function. The vendor module is responsible for calling
call-back function to notify the caller completion of vendor-specific shutdown
process.
Sample codes of sending a HCI_RESET command in the vendor-specific shutdown
process.
bug 7390787
Change-Id: I817c0a7dd57e750d38884746edeb3436cfc9cfd8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When factory Bluetooth device address is stored in the BT Controller's
non-volatile memory (e.g. BCM4330 OTP memory) instead of devices's file system,
the BDADDR will be retrieved from the Controller while enabling Bluedroid core
stack.
Introduce USE_CONTROLLER_BDADDR preprocessor directive in the vendor lib.
After patchram download, check whether the BT Controller has a non-zero's BDADDR
stored in its non-volatile memory. If not, write BTIF's init BDADDR to the
Controller.
bug 7340441
Change-Id: I2414b9479d4ef93ffd20c7ccc4875aab009e7cc8
|
| |
|
|
|
| |
Bug: 6837125
Change-Id: Ic3cc73f210e40d95b131a68244dc9e60bae80f37
|
| |
|
|
|
|
| |
This reverts commit d18044d184ebdbbdefe700ad439e1a4cead748f7
Change-Id: Ieb3f11f56c4368556b60c79c359a012fb8555a13
|
|
|
Bug: 6837125
Change-Id: I9e9d5a95463d5cd61a6e7f3b2f0a57c0b2f47e16
|