Hi Szymon, > Start Discovery was reporting 0 RSSI for invalid RSSI only for > BR/EDR devices. LE devices were reported with RSSI 127. > > Signed-off-by: Szymon Janc <szymon.janc@xxxxxxxxx> > --- > net/bluetooth/mgmt.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c > index f5c4d2e..a619d98 100644 > --- a/net/bluetooth/mgmt.c > +++ b/net/bluetooth/mgmt.c > @@ -7238,7 +7238,8 @@ void mgmt_device_found(struct hci_dev *hdev, bdaddr_t *bdaddr, u8 link_type, > * However when using service discovery, the value 127 will be > * returned when the RSSI is not available. > */ > - if (rssi == HCI_RSSI_INVALID && !hdev->discovery.report_invalid_rssi) > + if (rssi == HCI_RSSI_INVALID && !hdev->discovery.report_invalid_rssi && > + link_type == ACL_LINK) > rssi = 0; good catch actually. Which is the first kernel affected by this? Is this 3.18 or 3.19? Regards Marcel -- 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
