If I understand correctly, conn->power_save prevents the host stack from requesting active mode if it was not the host stack that requested sniff mode. I don't understand the motivation for this. If we have ACL data to send, then it seems like a good idea for the host stack to explicitly request active mode, regardless of the reason that we entered sniff mode. We want to enter active mode more aggressively when setting up SCO connections, to avoid a 5 second delay with certain sniff modes. But the conn->power_save code is getting in the way and doesn't appear to be useful in the first place. Sending patches in another email... Nick -- 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
