On Wed, May 7, 2014 at 7:17 AM, Lukasz Rymanowski <lukasz.rymanowski@xxxxxxxxx> wrote: > This patch introduce device method to start and stop connection monitor > and two new device properties ConnectionRSSI and ConnectionTXPower which > are tracked when monitor is active Does a polling API like this make more sense than just an "Update Connection Properties" method call? Why make new properties? The existing RSSI property could be re-used without confusion, likewise the TXPower property could be called just that - which would then give a place to fill in the TX Power if present in AD as well. Scott -- Scott James Remnant | Chrome OS Systems | keybuk@xxxxxxxxxx | Google -- 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
