From 5c95eff5ed022a30cd1194fe99744727691d3a48 Mon Sep 17 00:00:00 2001 From: Matt Ranostay Date: Tue, 30 Oct 2018 11:39:25 -0700 Subject: binding: bluetooth: add initial discovery filter support Allow clients to request devices only with certain profile UUIDs to be displayed in an discovery scan. This allows to filter out things like location tokens, smart scales, and etc which can't possibly have a2dp or hfp profiles for instance. NOTE: This is a write only setting. In the future should be read/write to see current discovery filters. Bug-AGL: SPEC-1630 Change-Id: Ic8b18656f84ac8047b170d6e601fcc2e63786af0 Signed-off-by: Matt Ranostay --- binding/bluetooth-bluez.c | 1 + 1 file changed, 1 insertion(+) (limited to 'binding/bluetooth-bluez.c') diff --git a/binding/bluetooth-bluez.c b/binding/bluetooth-bluez.c index 7640046..37c4469 100644 --- a/binding/bluetooth-bluez.c +++ b/binding/bluetooth-bluez.c @@ -147,6 +147,7 @@ void bluez_decode_call_error(struct bluetooth_state *ns, } else if (!strcmp(method, "StartDiscovery") || !strcmp(method, "StopDiscovery") || + !strcmp(method, "SetDiscoveryFilter") || !strcmp(method, "RegisterAgent")) { g_clear_error(error); -- cgit 1.2.3-korg