The ConnectionTXPower tracked here is hard to use without knowing the
maximum TX power of the controller, which can be obtained through the
same HCI command.
The device could also expose the maximum TX power as an attribute,
which can be set once on connection and does not need to be tracked
with this connection monitor API.
Regards,
Tim
Hi Tim,
On Wed, May 7, 2014 at 11:15 PM, Tim Song <[email protected]> wrote:
> The ConnectionTXPower tracked here is hard to use without knowing the
> maximum TX power of the controller, which can be obtained through the
> same HCI command.
>
Ok, I will add ConnectionTXPowerMax property in next version of this patch.
> The device could also expose the maximum TX power as an attribute,
> which can be set once on connection and does not need to be tracked
> with this connection monitor API.
>
> Regards,
> Tim
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
BR
Lukasz