Re: [RFC v10 09/10] Bluetooth: Auto connection and power on

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

 



Hi Marcel,

On Tue, Feb 18, 2014 at 5:55 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
> Hi Andre,
>
>> When hdev is closed (e.g. Mgmt power off command, RFKILL or controller
>> is reset), the ongoing active connections are silently dropped by the
>> controller (no Disconnection Complete Event is sent to host). For that
>> reason, the devices that require HCI_AUTO_CONN_ALWAYS are not added to
>> hdev->pend_le_conns list and they won't auto connect.
>>
>> So to fix this issue, during hdev closing, we remove all pending LE
>> connections. After adapter is powered on, we add a pending LE connection
>> for each HCI_AUTO_CONN_ALWAYS address.
>>
>> This way, the auto connection mechanism works propely after a power
>> off and power on sequence as well as RFKILL block/unblock.
>
> and when background scan is running, you might want to make sure to disable LE scan first before doing the actual power down. I just crashed my controller.

Hum, I didn't get any crash with my controllers. Could you send your kernel log?

BR,

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