summaryrefslogtreecommitdiffstats
path: root/Documentation/telephony
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2008-07-14 20:13:48 +0200
committerMarcel Holtmann <marcel@holtmann.org>2008-07-14 20:13:48 +0200
commit41a96212b3b7b3cd59e8e8d33e6dabf0e21d9778 (patch)
tree3ba680af5e3f984d7b32a25c4d71685a54541a8f /Documentation/telephony
parent333140b57fa7867bc92e5ee879b6ac4ef5e1d867 (diff)
downloadblackbird-op-linux-41a96212b3b7b3cd59e8e8d33e6dabf0e21d9778.tar.gz
blackbird-op-linux-41a96212b3b7b3cd59e8e8d33e6dabf0e21d9778.zip
[Bluetooth] Track status of remote Simple Pairing mode
The Simple Pairing process can only be used if both sides have the support enabled in the host stack. The current Bluetooth specification has three ways to detect this support. If an Extended Inquiry Result has been sent during inquiry then it is safe to assume that Simple Pairing is enabled. It is not allowed to enable Extended Inquiry without Simple Pairing. During the remote name request phase a notification with the remote host supported features will be sent to indicate Simple Pairing support. Also the second page of the remote extended features can indicate support for Simple Pairing. For all three cases the value of remote Simple Pairing mode is stored in the inquiry cache for later use. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'Documentation/telephony')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud