summaryrefslogtreecommitdiffstats
path: root/stack/gatt/gatt_attr.c
Commit message (Collapse)AuthorAgeFilesLines
* Bluetooth: Ignore unexpected notifications to cause disconnectionNitin Arora2015-10-231-0/+7
| | | | | | | | | | | | | The GattIf = 1 and the corresponding callbacks struct gatt_profile_cback is specifically used for GATT protocol connections by the stack and additionally for handling the service change indication registration when pairing to a remote device. The operation callbacks received on this Id disconnects the remote device if any indication/notification is received while this process is ongoing. This patch ignores such events. Change-Id: I04273f6a1ab5e2d74f49687c9a70670e40db9d39
* Disconnect Gatt during failure of service changed discovery processNitin Arora2015-06-171-0/+2
| | | | | | | | | | Gatt service changed discovery holds link till it completes discovery of service, characteristics, descriptots and writing notification for characteristic descriptor, this change takes care of removing the link if service discovery fails during any stage of this process. Bug: 21896912 Change-Id: Ie97a039568fedc66403895e7e917e4d72a5419e1
* Rectify allocation of GATT control blockNitin Arora2015-03-251-3/+6
| | | | | | | | | | This change ensures that a valid value is returned while requesting available control block or allocating memory for a new control block for saving GATT discovery handles. The bug if not fixed causes memory corruption and thus modifying some callback handles. Change-Id: I148ee82d2ea9fe77bebd34fd345b4fb6a6eee3cd
* LE: Register for service change indicationChaojing Sun2014-12-051-46/+269
| | | | | | | | | | | | Some bonded remote devices require the client to register for service change indication and actually set the client configuration descriptor before service change indications can be removed. This change add an additional step after device bonding has occured to register for service change indication if possible. Bug: 18173911 Change-Id: I25386faec0d58834ee2b0a9d1db2d2e052311264
* resolved conflicts for merge of b44cc59d to masterMatthew Xie2014-06-281-7/+7
|\ | | | | | | Change-Id: I74c86dd5a13d4cc0b225a4b1d516904c4382db74
| * Logging cleanup: AVRC, MCA, GATT, and SMP.Sharvil Nanavati2014-06-191-7/+7
| | | | | | | | Change-Id: I6d1e61ff023b5fd19f144955cff16831cc18c6e6
| * Merge BT 4.1 featuresGanesh Ganapathi Batta2014-04-301-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | LE: Add notification sent and congestion callbacks (2/4)Andre Eisenbach2014-06-251-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change introduces two new callbacks for applications to better handle LE notification flow control and transport congestion. The notification callback is invoked when the remote platform confirms an indication or when a local notification has been passed to the controller. No new notifications should be sent until a callback is received. Congestion callbacks are triggered when a GATT operation cannot be sent to the local Bluetooth controller. Repeatedly calling writeCharacteristic() for example will eventually trigger a congestion callback. Applications cannot send additional data until a further callback is received, indicating that the congestion has cleared up. Also fixes a memory leak issue that can trigger GKI exception for certain GATT operations. Change-Id: Ib470c15ca1f577573a632e9afe4cb9e86680fd8c
* | Merge BT 4.1 featuresGanesh Ganapathi Batta2014-05-061-6/+10
|/ | | | | | | | | | | | | | | | | | | 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
* Major warnings cleanupMike J. Chen2014-02-111-0/+3
| | | | | | | | | | | | 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>
* BLE HID device connection failure due to security error.Zhihai Xu2013-12-111-1/+2
| | | | | | | | | | | | | | | When HID BLE device start encryption, if some other GATT application already start encryption(but not finished yet) by calling gatt_security_check_start. The HID BLE device will be failed to start encryption, which will cause it to disconnect the BLE HID connection. The solution is to check whether we already started the encryption , If the encryption is already started, wait until the encryption finished, then continue to start security check for BLE HID device. add encrytion complete event to notify all GATT client encryption done. filter the event just for BTA HH LE GATT client. bug:11636246 Change-Id: If58e57c623cc8cfa05208587b010bec68c71306c
* Initial version of BLE support for BluedroidGanesh Ganapathi Batta2013-02-271-2/+2
| | | | Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
* Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879bafThe Android Open Source Project2012-12-121-0/+278
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-17 23:24:23 +0000