Hi Jakub, On Wed, Jul 22, 2015, Jakub Pawlowski wrote: > @@ -3564,9 +3564,10 @@ static int pair_device(struct sock *sk, struct hci_dev *hdev, void *data, > */ > hci_conn_params_add(hdev, &cp->addr.bdaddr, addr_type); > > - conn = hci_connect_le(hdev, &cp->addr.bdaddr, addr_type, > - sec_level, HCI_LE_CONN_TIMEOUT, > - HCI_ROLE_MASTER); > + conn = hci_add_to_sock_conn_whitelist(hdev, &cp->addr.bdaddr, > + addr_type, sec_level, > + HCI_LE_CONN_TIMEOUT, > + HCI_ROLE_MASTER); The purpose we're introducing this passive scanning functionality is so that we have a fresh RPA for the remote device. The way we know that a new RPA matches the remote device is by checking against an IRK. If the user is calling pair_device it means we don't have an IRK, so in this case it seems pointless to me to start passive scanning (not to mention that typically paired device is called straight after stopping an active scan). Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
