* [PATCH BlueZ 1/2] Write Link Loss Alert level if connected
@ 2011-08-09 16:47 Claudio Takahasi
2011-08-09 16:47 ` [PATCH BlueZ 2/2] Fix ATT disconnect callback not being called Claudio Takahasi
2011-09-27 8:25 ` [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Johan Hedberg
0 siblings, 2 replies; 3+ messages in thread
From: Claudio Takahasi @ 2011-08-09 16:47 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Claudio Takahasi
When SetProperty gets called for LinkLossAlertLevel, the alert level
can be written in the remote is the link is up.
---
proximity/monitor.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/proximity/monitor.c b/proximity/monitor.c
index 55d3985..c32ddec 100644
--- a/proximity/monitor.c
+++ b/proximity/monitor.c
@@ -396,6 +396,9 @@ static DBusMessage *set_link_loss_alert(DBusConnection *conn, DBusMessage *msg,
PROXIMITY_INTERFACE, "LinkLossAlertLevel",
DBUS_TYPE_STRING, &monitor->linklosslevel);
+ if (monitor->attrib)
+ write_alert_level(monitor);
+
return dbus_message_new_method_return(msg);
}
--
1.7.6
^ permalink raw reply related [flat|nested] 3+ messages in thread
* [PATCH BlueZ 2/2] Fix ATT disconnect callback not being called
2011-08-09 16:47 [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Claudio Takahasi
@ 2011-08-09 16:47 ` Claudio Takahasi
2011-09-27 8:25 ` [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Johan Hedberg
1 sibling, 0 replies; 3+ messages in thread
From: Claudio Takahasi @ 2011-08-09 16:47 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Claudio Takahasi
GAttrib disconnect function needs to be set after discovering the
primary services if the connection callback list is not empty. After
creating a device the connection can stay up, for this scenario the
registered disconnection callbacks are not being called.
---
src/device.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/src/device.c b/src/device.c
index 9dd657c..13749bf 100644
--- a/src/device.c
+++ b/src/device.c
@@ -1661,7 +1661,9 @@ static void primary_cb(GSList *services, guint8 status, gpointer user_data)
if (device->attios == NULL && device->attios_offline == NULL) {
g_attrib_unref(device->attrib);
device->attrib = NULL;
- }
+ } else
+ g_attrib_set_disconnect_function(device->attrib,
+ attrib_disconnected, device);
g_slist_free(uuids);
--
1.7.6
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH BlueZ 1/2] Write Link Loss Alert level if connected
2011-08-09 16:47 [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Claudio Takahasi
2011-08-09 16:47 ` [PATCH BlueZ 2/2] Fix ATT disconnect callback not being called Claudio Takahasi
@ 2011-09-27 8:25 ` Johan Hedberg
1 sibling, 0 replies; 3+ messages in thread
From: Johan Hedberg @ 2011-09-27 8:25 UTC (permalink / raw)
To: Claudio Takahasi; +Cc: linux-bluetooth
Hi Claudio,
On Tue, Aug 09, 2011, Claudio Takahasi wrote:
> When SetProperty gets called for LinkLossAlertLevel, the alert level
> can be written in the remote is the link is up.
> ---
> proximity/monitor.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
Both patches have been applied. Thanks.
Johan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-09-27 8:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-09 16:47 [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Claudio Takahasi
2011-08-09 16:47 ` [PATCH BlueZ 2/2] Fix ATT disconnect callback not being called Claudio Takahasi
2011-09-27 8:25 ` [PATCH BlueZ 1/2] Write Link Loss Alert level if connected Johan Hedberg
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.