[PATCH BlueZ v1] device: Fix not setting DEVICE_FLAG_REMOTE_WAKEUP when required

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>

Due to the introduction of DEVICE_FLAG_ADDRESS_RESOLUTION it is no
longer possible to check if the kernel has support for it ahead of time
since that would depend on device->supported_flags which is only updated
with MGMT_OP_ADD_DEVICE _after_ services are probed.

Fixes: https://github.com/bluez/bluez/issues/1207
---
 src/device.c | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/src/device.c b/src/device.c
index 2ee319c4f7c2..c364d72c3bdf 100644
--- a/src/device.c
+++ b/src/device.c
@@ -1552,12 +1552,6 @@ static bool device_get_wake_support(struct btd_device *device)
 
 void device_set_wake_support(struct btd_device *device, bool wake_support)
 {
-	if (device->rpa && !btd_adapter_has_exp_feature(device->adapter,
-						EXP_FEAT_RPA_RESOLUTION)) {
-		warn("Unable to set wake_support without RPA resolution");
-		return;
-	}
-
 	device->wake_support = wake_support;
 
 	if (device->wake_support)
-- 
2.49.0





[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux