BlueZ: btd_profile callbacks not being triggered properly for LE devices ?

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

 



Hi,

struct btd_profile contains folowing callbacks:
.connect
.disconnect
.device_probe
.device_remove
.accept

I noticed that those callbacks:
.device_probe
.device_remove
.accept

are called properly, but:
.connect
.disconnect

callbacks are not being called at all when LE device disconnected
itself or was connected or autoconnected back. There is no doc, but
I'm guessing those should be triggered in this cases, right ? Also,
when I connect first time to a device, only .accept should be
triggered, but when I connect next time only .connect ?
Can you please explain what is the intended order of those callbacks ?
Then I can fix them if I find some discrepencies from intended
behaviour.

Jakub
--
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