1. 05 3月, 2015 1 次提交
    • J
      Bluetooth: fix service discovery behaviour for empty uuids filter · 82f8b651
      Jakub Pawlowski 提交于
      This patch fixes service discovery behaviour, when provided uuid filter
      is empty and HCI_QUIRK_STRICT_DUPLICATE_FILTER is set. Before this
      patch, empty uuid filter was unable to trigger scan restart, and that
      caused inconsistent behaviour in applications.
      
      Example: two DBus clients call BlueZ, one to find all devices with
      service abcd, second to find all devices with rssi smaller than -90.
      Sum of those filters, that is passed to mgmt_service_scan is empty
      filter, with no rssi or uuids set.
      That caused kernel not to restart scan when quirk was set.
      That was inconsistent with what happen when there's only one of those
      two filters set (scan is restarted and reports devices).
      
      To fix that, new variable hdev->discovery.result_filtering was
      introduced. It can indicate that filtered scan is running, no matter
      what uuid or rssi filter is set.
      Signed-off-by: NJakub Pawlowski <jpawlowski@google.com>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      82f8b651
  2. 28 2月, 2015 1 次提交
  3. 21 2月, 2015 1 次提交
  4. 19 2月, 2015 4 次提交
  5. 15 2月, 2015 1 次提交
  6. 02 2月, 2015 2 次提交
  7. 31 1月, 2015 1 次提交
  8. 29 1月, 2015 1 次提交
  9. 24 1月, 2015 1 次提交
  10. 16 1月, 2015 1 次提交
  11. 13 1月, 2015 1 次提交
  12. 03 1月, 2015 1 次提交
  13. 21 12月, 2014 1 次提交
  14. 20 12月, 2014 3 次提交
  15. 19 12月, 2014 2 次提交
  16. 05 12月, 2014 3 次提交
  17. 03 12月, 2014 7 次提交
  18. 19 11月, 2014 1 次提交
  19. 18 11月, 2014 1 次提交
  20. 15 11月, 2014 2 次提交
  21. 03 11月, 2014 1 次提交
  22. 02 11月, 2014 1 次提交
  23. 25 10月, 2014 2 次提交
    • A
      Bluetooth: Defer connection-parameter removal when unpairing · 89cbb063
      Alfonso Acosta 提交于
      Systematically removing the LE connection parameters and autoconnect
      action is inconvenient for rebonding without disconnecting from
      userland (i.e. unpairing followed by repairing without
      disconnecting). The parameters will be lost after unparing and
      userland needs to take care of book-keeping them and re-adding them.
      
      This patch allows userland to forget about parameter management when
      rebonding without disconnecting. It defers clearing the connection
      parameters when unparing without disconnecting, giving a chance of
      keeping the parameters if a repairing happens before the connection is
      closed.
      Signed-off-by: NAlfonso Acosta <fons@spotify.com>
      Acked-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      89cbb063
    • A
      Bluetooth: Include ADV_IND report in Device Connected event · fd45ada9
      Alfonso Acosta 提交于
      There are scenarios when autoconnecting to a device after the
      reception of an ADV_IND report (action 0x02), in which userland
      might want to examine the report's contents.
      
      For instance, the Service Data might have changed and it would be
      useful to know ahead of time before starting any GATT procedures.
      Also, the ADV_IND may contain Manufacturer Specific data which would
      be lost if not propagated to userland. In fact, this patch results
      from the need to rebond with a device lacking persistent storage which
      notifies about losing its LTK in ADV_IND reports.
      
      This patch appends the ADV_IND report which triggered the
      autoconnection to the EIR Data in the Device Connected event.
      Signed-off-by: NAlfonso Acosta <fons@spotify.com>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      fd45ada9