From 570a5505fc79c16ad69f79d6db57ee79e409828a Mon Sep 17 00:00:00 2001 From: Luiz Augusto von Dentz Date: Tue, 29 Apr 2025 12:12:32 -0400 Subject: [PATCH] device: Fix not setting DEVICE_FLAG_REMOTE_WAKEUP when required 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 2ee319c4f..c364d72c3 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.47.3