| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\|
| |
| |
| | |
Change-Id: Ibc6d6e691b7f97611d16f96220346dfd6ffbbf52
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some standard library functions are used while relying on bionic headers
including the headers the functions were actually declared on. Add those
missing #includes so that bluetooth.default.so will compile on glibc.
Change-Id: Ied9f89ce5a05911fca63f6bfe1b8cc8196ab3b1c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change uses generic format specifier for logging the
pointers which can be 64 bit or 32 bit depending upon the
system used for compilation.
Also address of operator is used before casting a int variable
to void pointer.
Change-Id: Ie9dec408f3a5f674079f77c047d8192f65a004ca
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On some controllers, reading extended local feature pages can fail,
leading to an assertion and subsequent stack crash. To work around this
issue, the HCI command response status checked has been moved to
individual HCI command handlers, where the same assert is raised. Only
for extended local feature responses do we simply ignore any failure
(for now).
Bug: 20057316
Change-Id: I8601ecbdef07921edfe13d42d1f24110bc8ba535
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change uses generic format specifier for logging the
pointers which can be 64 bit or 32 bit depending upon the
system used for compilation.
Also address of operator is used before casting a int variable
to void pointer.
Change-Id: Ie9dec408f3a5f674079f77c047d8192f65a004ca
|
|/
|
|
| |
Change-Id: I0d3e93ea61dd03505fe9db902ed90bdd4141cab2
|
|
|
|
| |
Change-Id: I60d87da42fa28dd57d50384396e30504103d1ae5
|
|
|
|
| |
Change-Id: I9b99111f50dc4f1c581ef96e78b36d14b51a6866
|
|
|
|
|
|
| |
This fixes include path issues for libbt.
Change-Id: I416f563c0056216e86898d8e9cc111b600c73ce0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hardware error was caused due to a faulty HCI command formed in the
process of vendor specific pre-SCO setup in the stack(set_audio_state)
Fixed the above problem and also added back the vendor (interface)
mapping for the set_audio_state functionality to facilitate the
sending of the pre-SCO vendor specific commands.
Made common vendor library audio setting by moving to hci subsystem.
General cleanup around this functionality.
Bug: 19923226
Change-Id: I4a743f6725459f360bd2a90e0a46f08fcca2292d
|
|
|
|
|
|
| |
This reverts commit 4d8ac4ff015ff87c4e985ac0d9a5f3c2a6b0d9fa.
Change-Id: Ie1433c82014b6ddce78c5363100ab109ae0fecde
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hardware error was caused due to a faulty HCI command formed in the
process of vendor specific pre-SCO setup in the stack(set_audio_state)
Fixed the above problem and also added back the vendor (interface)
mapping for the set_audio_state functionality to facilitate the
sending of the pre-SCO vendor specific commands.
Bug: 19923226
Change-Id: I03c6a1c048c21549b7326a783b70588686283eb3
|
|
|
|
| |
Change-Id: I0e8af541bf9c5837d92b5ccc047b3dd9d3765767
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Split events and acl data in hci dispatch, and dispatch events by event code
Future code will now be able to dynamically tie into hci events, instead
of relying on a hard coded routing.
|
|
|
|
|
| |
Waited for the merge to complete before reworking
the feature into the stack.
|
|
|
|
|
| |
Also includes simple tests for it + disambiguates
including hash_function.h throughout the stack.
|
|
|
|
|
|
| |
This will allow us to do deeper equality on things like
bluetooth addresses where the actual pointers are different
but the values of the bluetooth addresses are the same.
|
| |
|
| |
|
|
|
|
|
|
| |
These macros should replace ALOG* and the various trace macros
used throughout bluedroid. This change eliminates all uses of the
ALOG* macros in favor of the new ones.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the hci layer ever entered the ignore state,
synchronization death was immenent. This patch fixes that.
Also adds additional info print out when entering the ignored state.
Adds tests for the ignored state.
Doesn't solve the problem of why we were getting NULL back from
the buffer allocator, though. (The trigger for the ignored state.)
Bug: 18156298
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
BLE supported states was moved to controller during the callback
re-factoring CL, but in the commotion I forgot to remove the
supported states variable from devcb.
This meant I didn't realize GAP was looking at the wrong place
for BLE supported states. This CL fixes that.
|
|
|
|
|
| |
Don't require a vendor library command transmit to provide a callback.
If the vendor library provides a null callback just ignore it.
|
|
|
|
|
|
|
| |
Happened to be ok on devices with 1 or 2 feature pages, but for
devices with 3 or more feature pages it was always loading the
page at index 1 for pages past the page at index 0, causing
an infinite loop, causing bluetooth enable to time out.
|
|
|
|
|
|
| |
* 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
|
|
|
|
| |
This will allow the controller restart sequence to be serialized into a single function.
|
|
|
|
|
|
| |
Shutdown is managed by the stack manager now, so we don't need to lock
around it. The fetching of the device address is a bit hacky right now,
until it becomes part of its own module.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Moves stack config out of the combined bte_config, and into
its own module.
Makes btsnoop more self sufficient and removes uneccessary
levels of indirection.
Refactor logging slightly into a (temporary) module to disassociate
from the direct calls from config. Eliminates some useless stuff in
the module as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
an ACL packet
During the startup process, commands are sent before the ACL sizes are fetched.
With the change that we now assert the acl sizes are fetched when you request
them from the controller, the assertion was being triggered during that phase.
When I was rebasing the waiting changes and also making the assertion change,
I should have been more careful to test this. mea culpa
Also simplifies that code path just a bit.
|
|
|
|
| |
No actual code additions/deletions, other than additional forward declarations
|
|
|
|
|
|
|
| |
Moves all HCI initialization into hci_layer. Removes superfluous exposed
functionality on the HCI layer (like turning the chip on/off and logging)
Also reorganizes some of hci_layer to group related functions together.
|
|
|
|
|
|
|
| |
Refactor the hci layer to use it.
The timer wrapper allows you to specify the duration, etc at construction time
rather than at start time, making some usage patterns of alarm more convenient.
|
|
|
|
|
|
|
|
| |
- x_interface_t started to get annoyingly verbose, changed to x_t
- buffer_allocator is standalone now, no longer part of bte_main
- new controller_t to handle controller start up and hold controller state
- new hci_packet_factory to make packets, and hci_packet_parser
to read information out of packets.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
There was a mismatch where the free function was GKI_free for a
pointer allocated with osi_calloc. This resulted in GKI exceptions
being thrown if the adapter goes through enable -> disable -> enable
-> disable without terminating the process.
|
| |
|
|
|
|
| |
And found a memory leak in config, so it's doing its job! :)
|
| |
|
| |
|
| |
|
|
|
|
| |
Unit tested. Needs verification on actual device (i.e. HDP profile).
|