Commit: 138ac9faaeb525446ac6e2e5000bd764737685fa
Parent: c1c440e5bfb1d6337ecb2a3aef18827af1d6bc31
Author: Andre Guedes <andre.guedes@openbossa.org>
Committer: Johan Hedberg <johan.hedberg@intel.com>
Date: 2012-02-09 12:48:53
Tree: f2352cd1a12904be6f15fe50047eab970d399e6e

device: Reply ATT requests during bonding Unlike BR/EDR which has a dynamically allocated L2CAP data channel, LE has a fixed L2CAP channel where data are transmitted (CID 4). This means that once the LE link is established the remote device is able to send data (ATT messages) to the local device. Due to the ATT sequential request-response protocol, once a client sends a request to a server, that client shall send no other request to the same server until a response PDU has been received. If the response PDU arrives in 30 secs the remote device disconnects. This way, in order to be able to reply ATT requests which may come through channel ID 4 during the pairing, we first establish an ATT connection and then we start the pairing process. That issue was discovered during test sessions in UPF. We found some LE devices sending ATT Requests in CID 4 while pairing was still in progress

Diffstat

M src/device.c | 47 ++++++++++++++++++++++++++++++++++++++++

1 files changed, 47 insertions(+), 0 deletions(-)

View Full Diff | Patch