Re: [PATCH 6/8] proximity: link loss: implement link loss server

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

 



Hey Anderson,

On Wed, Mar 14, 2012 at 15:09, Anderson Lizardo
<anderson.lizardo@xxxxxxxxxxxxx> wrote:
>> +       lladapter->watch = g_dbus_add_signal_watch(lladapter->conn,
>> +                               BLUEZ_SERVICE, NULL, DEVICE_INTERFACE,
>> +                               "DisconnectRequested", handle_local_disconnect,
>> +                               lladapter, NULL);
>
> Does this also work if the device is removed locally with:
>
> * test-device remove ?
> * when bluez is shutting down?
> * user disables the adapter locally?

test-device should work - it uses Device.Disconnect(), which is
precisely the function that emits this signal.
When bluez or the adapter is shutdown the unregister_link_loss()
function is called, where we clear everything anyway.

>
> Also, listening to a d-bus signal of the process itself looks strange.
> Did you try the device_add_disconnect_watch() call instead?

Actually I wasn't aware of device_add_disconnect_watch() at the time.
It does look cleaner. I'll rewrite this part.

Thanks,
Arik
--
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


[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