01a069a228cb63988e502aed01a73a2a1d8a59eb |
|
17-Dec-2014 |
Andre Eisenbach <eisenbach@google.com> |
Allow connection parameters updates by slave GATT service discovery in the slave role does not update to fast connection parameters when connected. Accordin to the 4.0 spec, the connection parameter disable/enable call is used for only by the masster role. The 4.1 and later spec allows the slave role to control the connection parameter update so that a slave role GATT client can perform the service discovery using fast connection parameters. Also switched to requestiong 7.5ms connection interval by default during service discovery. Bug: 18266904 Change-Id: Ie6300587306be3d694937e3888069e252592be42
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
472c2a7bb0ac070e596084f9422157f7872c6dca |
|
23-Oct-2014 |
Prerepa Viswanadham <dham@google.com> |
Don't starve a BT ACL link with 0 xmit quota With new link management of controller buffers between different ACL connections, it is possible that a ACL conn would get 0 buffers - thus no profile can run. This affects classic and LE ACL connections. This work around allows a floor of 1 buffer as the floor for all connection, irrespective of controller capability. Bug: 17976311 Change-Id: I7cd0d34af47c441c5ea7f2b836b591a4fec62ad1
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
97e75b73a57602b7d9771f28216630ba32fd702a |
|
08-Oct-2014 |
Chaojing Sun <cjsun@broadcom.com> |
LE: Serialize multiple connection parameter update requests 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
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
d5aa24750c2202ce944560c2c27ead0214e8350d |
|
24-Sep-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Peer device's latest RPA is not being applied The latest discovered address is not used when reconnecting to devices using resolvable private addresses, if RPA resolution offloadin is not supported in the controller. This patch also address the exception case where BT off is memseting all control value while the IRK list is still being cleaned up. Bug: 17187661 Change-Id: Ifeb5b8297e7eadb0e34ec1afbd41f46bdd836cf3 Author: Chaojing Sun <cjsun@broadcom.com>
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
7ae25156f4250af9d0e8cd8d559d916cfb847feb |
|
11-Sep-2014 |
Prerepa Viswanadham <dham@google.com> |
Avoid premature LE connection notifaction to app To avoid premature connection notification to app, always wait for LE read remote feature complete with success before the connection event is sent to application. This patch also deprecates the BTA_SKIP_BLE_READ_REMOTE_FEAT flag. Since the remote feature request is now serialized and start encryption won't be called until the connection is up, this flag is no longer necessary and interferes with the new behaviour. This is an extension of previous CL Bug: 17326529 Change-Id: Icfd4c5dfdd9f89d1318ef429e132eb005abb1f64
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
92ac2d8919f8e38a091903270eb5500073d67d4b |
|
11-Jul-2014 |
Mudumba Ananth <ananthm@broadcom.com> |
LE link_xmit_quota is not correctly allocated LE link transmit quota should be calculated based on the total LE buffer available and number of LE link that shares the buffer. Currently it's been calculated based on the ACL buffer number and total physical links(BR and LE), that cause the LE link transmit quota not being done right. Modify the link transmit quota allocation, and keep track of LE link seperately, also keep track of round robin scheme for LE links solving the problem. Bug: 16560957 Change-Id: I70f91827b96f2c10421e91311ea34cc81a5ef4b8
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
9c29d08bc7c6da33db5cfc777404354c6dca845c |
|
03-Sep-2014 |
Priti Aghera <paghera@broadcom.com> |
Avoid premature LE connection notifaction to app To avoid premature connection notification to app, always wait for LE read remote feature complete with success before the connection event is sent to application. bug 17326529 Change-Id: Id731bf02e8d5d5a68db12e0478b8eb74723eb95d
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
16fe0822ccd3eb6f66d3afd9965d25a0a0cb4c30 |
|
07-Aug-2014 |
Prerepa Viswanadham <dham@google.com> |
Use run time parameters to control LE features Use values read from controller to enable and control LE features such as multi advertising, RPA offload, maximum irk size etc bug 15393216 Change-Id: I193e2b9a0dc61b86f667e986803571440e390160
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
f37456d5a14773e25386629803f7dcaecb37fb99 |
|
04-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Fix random address resolution when done in the stack If the local device does not support random address resolution in the Bluetooth chip, it has to be performed in the host stack. This patch fixes some instances where address resolution was not performed properly, causing device reconnection to fail. Change-Id: Ifb84a9fa44995caa3680d9a0b4248ef911eb9ad0
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
43c6a47303866bad6a0338ed53cf38f1a779a498 |
|
02-Jul-2014 |
Wei Wang <weiwa@google.com> |
am b3c61229: Merge "Code cleanup - remove unnecessary commented out code" into klp-wireless-dev * commit 'b3c61229ccf38ea3f398f93902d348ba12a7fb07': Code cleanup - remove unnecessary commented out code
|
51f35b04d40ec65fd478fe366d041a649ad09760 |
|
02-Jul-2014 |
Wei Wang <weiwa@google.com> |
Code cleanup - remove unnecessary commented out code Change-Id: I86e78d1b0470b9fda7455ae8ef5788814cf5c780
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
847b706a9cfba9dc749240b33276a7e02df30f29 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of a51c9d9d to master Change-Id: I50eec2efe06017bddac291846fa098c26dc10da1
|
9c07b33b335dfa3b4357f9ee293e1c1c03a7389a |
|
20-Jun-2014 |
Steve Paik <spaik@google.com> |
[bluedroid] Fix slave latency and conn timeout defaults in BLE The default connection parameters were not being applied properly in BLE. Also fixed a typo in btm_ble.c. Change-Id: I6cfb0f2a400740578910dcf4c7192ea16406aa1b Signed-off-by: Steve Paik <spaik@google.com>
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
a51c9d9d225e41fe36a0133f1c17fd981ea59c1d |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: L2CAP and SDP. Change-Id: I62b5d4f330312dc466a758cb554952017f899696
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
d8ab91712132bc3e03f01be1a73e557588094a0d |
|
02-Jun-2014 |
Adam Hampson <ahampson@google.com> |
Merge "fix compliation when BLE_VND_INCLUDED is false"
|
845c2601ece4c2323a03c6d705cd16545f6df08a |
|
27-May-2014 |
Adam Hampson <ahampson@google.com> |
fix compliation when BLE_VND_INCLUDED is false Change-Id: I48785d6d36965fb03657523ee6eb48cb63fd5364 Signed-off-by: Adam Hampson <ahampson@google.com>
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
66988a022d219f5385b3f76e3ae26566ad80fb86 |
|
29-May-2014 |
Nitin Arora <niarora@codeaurora.org> |
This patch contains bug fixes for solving race conditions for multiple advertisers and incorrect VS command length which makes uuid filters not working. b/15094154, b/15174583 Change-Id: I78746b923301fa47afb21f8bedb0d79b42f492b9
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
fa994c9b7d63d381e33a5d63a7c97ae3edf4dc0f |
|
29-May-2014 |
Nitin Arora <niarora@codeaurora.org> |
Bluetooth: Changes to enable features on KWD This patch contains changes needed to enable features, multiple advertisment, packet content filtering and privacy mode on kwd branch Change-Id: If95bfb38eafe26f16db20e7650865c2f19553548
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
ed534e330bf63c72e778fc8daae09ddd63c395b2 |
|
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "Revert "LE: Add RRA offloading and vendor specific PCF commands"" This reverts commit 146bb736bc1cdfd679bbafcf3f33c7af612096b9. Change-Id: Ie4e6b4d7118a622d04c46623add1073906366edf
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
146bb736bc1cdfd679bbafcf3f33c7af612096b9 |
|
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "LE: Add RRA offloading and vendor specific PCF commands" This reverts commit 15fa3be8ecd576b9ef88e20cf9a6f4bd765cbc6b. Change-Id: Iaa484508ac664d4cb6c94758c2984d53263a902a
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
15fa3be8ecd576b9ef88e20cf9a6f4bd765cbc6b |
|
12-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Add RRA offloading and vendor specific PCF commands Change-Id: Iadca8e73ceaadcd0429421ea70f1b76644e88c42
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
0943c10ed5713a08659f08e39e13de4894aaba61 |
|
12-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Add RRA offloading and vendor specific PCF commands Change-Id: Iadca8e73ceaadcd0429421ea70f1b76644e88c42
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
7fa4fba6f59f97df00aff07dbe8fb21b114b3c2c |
|
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features 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 Conflicts: stack/btu/btu_hcif.c
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
8fe58875ce67c6e1099e7ba2339dcd2b979491b0 |
|
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features 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
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
6f908b2cf977794342ce661d99c7d45b03dc6f58 |
|
11-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
support resolve BLE random mac address for both central and peripheral mode. bug:12990335 Change-Id: Ica42dcf039487b7b01454ce9255f3f6fae2faaaf
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
8b35b3fccc065730e6f0ee1050d3e4528e58ea37 |
|
11-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
support resolve BLE random mac address for both central and peripheral mode. bug:12990335 Change-Id: Ica42dcf039487b7b01454ce9255f3f6fae2faaaf
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
5cd8bff2dd0337cb52bf48f312e3d2d55a8882fb |
|
01-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Major warnings cleanup Mostly fixing unused parameter warnings. A few other warnings also fixed like possible use of unitialized variables (no real issue found, just compiler couldn't follow the path), signed vs unsigned warning. Also fixed some typos, indent issues, removal of dead code, etc. Change-Id: I95eb887aefc4d559d7921f71a0af5f3bfb01ac01 Signed-off-by: Mike J. Chen <mjchen@google.com>
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
15d0a0c580ba8940133b2d0977176e8e30ffe6a5 |
|
18-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
BLE stack doesn't handle multiple l2cap_conn_update requests we can define 4 bits as flags: 1. L2C_BLE_CONN_UPDATE_DISABLE: if set it means disable update connection parameter. otherwise enable 2.L2C_BLE_NEW_CONN_PARAM: if set, it means we have new connection parameter which is needed to be configured if possible(after update done or enable). 3.L2C_BLE_UPDATE_PENDING: if set, it means waiting for connection parameter update finished. this flag will be cleared in btu_ble_ll_conn_param_upd_evt. will be set when we call btsnd_hcic_ble_upd_ll_conn_params 4.L2C_BLE_NOT_DEFAULT_PARAM: if set, it means we don't use the default connection parameter. so when we disable update, we need to configure default connection parameter. with these 4 flags, we can replace all these states: UPD_ENABLED, UPD_DISABLED, UPD_PENDING and UPD_UPDATED. so we can cover all the corner cases which aren't handled by original code. bug:11450715 Change-Id: I6673d4783a8063bf9e8a213c6669800f86e67945
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
51d5f6393615aad6683d3d2ed0f82ed51e29aa9d |
|
17-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
sometime the BLE connection parameter isnot updated for the first time When we receive the BLE connection parameter update from remote device after smp_send_pair_req before start BLE service discovery(bta_gattc_set_discover_st). We will miss update this BLE connection parameter. The reason is we call L2CA_EnableUpdateBleConnParams(p_cb->pairing_bda, FALSE); in smp_send_pair_req ,We change the state to UPD_DISABLED. When we receive the new BLE connection parameter from remote device, we will update the state to UPD_PENDING, which will update the new connection parameter when enable the connection parameter update. when we start BLE service discovery we call L2CA_EnableUpdateBleConnParams(p_srcb->server_bda, FALSE); in bta_gattc_set_discover_st, We will update the state back to UPD_DISABLED, which will cause we miss updating the new connection parameter when enable the connection parameter update. The fix is don't change the state to UPD_DISABLED when the state is UPD_PENDING for disabling. bug:11727252 Change-Id: I953b9ca669e3460e18b340e7779cc54e03d6305b
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
3dc5945f1d62f9d30c7fcd4b1fe4077a3ba2f605 |
|
26-Oct-2013 |
Zhihai Xu <zhihaixu@google.com> |
A typo to set wrong max connection interval value when we create a BLE connection. when we set the max connection interval value, we should use BTM_BLE_CONN_INT_MAX_DEF instead of BTM_BLE_CONN_INT_MIN bug:11390678 Change-Id: Ia3f6d5e9cb91b2e998d014ed4849eff8455af770
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
6975b4d711142b885af479721cada448952c6b41 |
|
06-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: UPF 45 bug fixes This change fixes the following issues: - Second GATT-over-BR/EDR channel cannot be established when there already is an existing GATT-over-BR/EDR channel - If encryption fails for an LE connection due to a missing key, the security state is not being cleared and blocks all further security processing - When DM discovery of an LE Peripheral device fails with a connection timeout, no further discovery requests can be made - GATT service discovery can get into endless loop when duplicate descriptor definitions are found on the remote device - When GATT over BR/EDR fails, BTA does not give a connection callback to the application initiating the connection - BR/EDR connection to remote platform does not generate API callbacks - Stack crash discovered during UPF after remote disconnects - The host is sending HCI disconnect to invalid HCI handle when SMP fails because of a connection timeout - Possible race condition: If a disconnect is immediately followed by a connection complete, the connection complete cannot be processed in the BTA GATT state machine - Write Complete event is not triggered for Prepare Write requests Change-Id: I539cdedd68007818ff4f0d0213cee1c913f72d0f Conflicts: bta/gatt/bta_gatts_act.c
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
12c3f496c3612472a22cbb0afd89812b154b4186 |
|
25-Apr-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Fix shared ACL buffer allocation Allocate a static amount of LE buffers for chipsets that do not provide separate ACL buffers for LE and BR/EDR. Bug: 8714387 Change-Id: I74e954c0824ddfd89b50c14f6848db787f9b9bff
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
0082e027d5ae3f45a3a613ed720c31e35f61d0eb |
|
03-Apr-2013 |
Andre Eisenbach <andre@broadcom.com> |
Fix LE buffer size for 0 length buffers If the local chip reports 0 LE data buffers and 0 LE ACL data package length, then the default ACL buffer length as returned byt the Read_Buffer_Size command is to be used instead. Change-Id: I953fabe426a98cc1b005d3b46c3e7f227c23a686
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
|
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|
5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/external/bluetooth/bluedroid/stack/l2cap/l2c_ble.c
|