Hi Lukasz, On Fri, Mar 28, 2014 at 5:37 AM, Lukasz Rymanowski <lukasz.rymanowski@xxxxxxxxx> wrote: > If we go with v3, then in Android case we will need to add more logic > to bluetoothd to cover case when Application calles Read Remote Rssi > only once. We just need to avoid letting kernel to poll without the reason. > However I do expect android application to call this read remote rssi in > a loop anyway. One way to do that is to have a "timeout" timer (e.g. 5 seconds) that is reset on each read_remote_rssi call from HAL. On this timer expires, Unregister is called. Note that the comment I made on the patch itself regarding configuring the period for readings apply here: I think there should be some way to set this period. Otherwise, a two small period (say, 1s) will be wasting power for an application that reads only every 5s or 10s. Or the contrary, a too long timer will make applications which read more frequent receive inaccurate readings. Best Regards, -- Anderson Lizardo http://www.indt.org/?lang=en INdT - Manaus - Brazil -- 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
