summaryrefslogtreecommitdiffstats
path: root/stack/include/btu.h
Commit message (Collapse)AuthorAgeFilesLines
* Remove more GKI code.Sharvil Nanavati2015-03-161-9/+0
| | | | | This change removes all remaining GKI task remnants as well as a few timer and buffer bits.
* Don't call GKI_send_event on BTU task since it's not a GKI task anymore.Sharvil Nanavati2015-03-161-5/+0
|
* Remove GKI timersSharvil Nanavati2015-03-161-7/+0
|
* Remove unused ACL packet size getters, remove unused timer entityZach Johnson2015-03-161-3/+0
|
* Remove some remaining references to OBXZach Johnson2015-03-161-6/+0
| | | | | | | | | | | | Android implements the Object Push Profile in java against RFCOMM sockets with its own implementation of OBX there. OBX in Bluedroid isn't compiled, and is missing header files required to compile it anyway. Removed a number of OBX related headers and updated a few references where they were used out of place. Change-Id: Ifaecfb6f85b1dca9055932886af484b6dc107fc1
* Refactor btm_devctl reset sequenceZach Johnson2015-03-161-10/+0
| | | | | | * Controller bring up on blockable thread now * Removed some duplicate and commands during controller bring up * The code to make commands for controller bring up is smaller and better
* Removing unnecessary BTAPI #defines.June R. Tate-Gans2015-03-161-18/+18
|
* Remove unused hci_cmd_cb in btuZach Johnson2015-03-161-12/+0
| | | | | An earlier change obviated the need for it, but I forgot to remove it at that time.
* Remove btu_task and replace with bt_workqueue reactorChris Manton2015-03-161-5/+5
|
* Sink all HCI transmission management into the HCI layerZach Johnson2015-03-161-6/+19
| | | | | | | | | | | | Begins the refactoring of the HCI related code in BTA, corrects some hacks in the HCI layer (no more concept of internal commands, yay!), and corrects the handling of multiple commands pending response in the HCI layer. This introduce a horrible hack external to the HCI layer to keep BTU HCI handling of command complete/status events on the BTU task. That hack will be removed when BTU moves to a reactor model and we have osi threads to work with.
* GKI task entry points should have a consistent signature.Sharvil Nanavati2015-03-161-1/+1
| | | | | | | | | | | | | Previously, GKI task entry points had inconsistent signatures. For example, we had: int btif_media_task(void *p) void btif_task(UINT32 params) void btu_task (UINT32 param) The single argument was universally ignored and the caller always set it to 0. This change consolidates all of that and defines the entry point as having 0 arity and no return value.
* Move BTU task creation into stack/btu/btu_init.c.Sharvil Nanavati2015-03-161-1/+5
| | | | | Also fixed function naming where the BTE prefix was used instead of BTU.
* Remove unused BTU timer/event APIsChris Manton2015-03-161-1/+0
| | | | | | | btu_register_timer btu_deregister_timer btu_register_event_range btu_deregister_event_range
* Remove unused #define BTU_CMD_CMPL_TOUT_DOUBLE_CHECKChris Manton2015-03-161-3/+0
|
* Release GATT resources upon teardownChris Manton2015-03-161-0/+1
|
* LE: Serialize multiple connection parameter update requestsChaojing Sun2014-10-151-5/+3
| | | | | | | | | | Bluetooth controllers do not allow multiple connection parameter updates where there is one outstanding. This requires serializing all connection parameter update requests and send the latest request when the pending one is finished. Bug: 17979666 Change-Id: Ic49bd89a4ded28014d74b40e67f2a3ea490b9ef7
* BLE privacy timerChris Manton2014-06-241-0/+4
| | | | | | | | | Adds another timer with one-shot characteristic that allows for variable firing of alarms. Change the BLE privacy code to use this timer rather than the BTU continuous timer. Change-Id: I6baa4e6a76813285c15f24aeb3c7ef942ed01858
* Remove dead timer code from btuChris Manton2014-06-111-5/+0
| | | | Change-Id: I28fb3fb64546aac6e08886f71f80fdeaf86fc5af
* Merge BT 4.1 featuresGanesh Ganapathi Batta2014-04-301-3/+8
| | | | | | | | | | | | | | | | The features include: - LE Peripheral Mode - Link Layer topology (LE Central & Peripheral Concurrency) - Dual Mode Topology (Ability to choose LE transport when connecting with other Dual Mode devices) - Fast advertising Interval - Limited Discovery Time Changes - GAP Authentication and Lost Bond - Dual Mode Addressing - Common Profile and Service Error Code - 32 bit UUIDs Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42
* Initial version of BLE support for BluedroidGanesh Ganapathi Batta2013-02-271-1/+5
| | | | Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
* Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879bafThe Android Open Source Project2012-12-121-0/+310
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-21 22:36:12 +0000