Re: [RFC 7/7] Update Management API documentation

Hi,

On Thu, Jun 16, 2011 at 9:07 AM, Ganir, Chen [off-list ref] wrote:

quoted

if TX power is only read once than the kernel should just do it once
and
be done with it.

And for RSSI, it would be better if the kernel read this periodically
based on current sniff mode etc. Userspace can not trigger this with
proper timing anyway. And it will potentially at some point start
blocking the controller. Only the kernel really knows when it is
acceptable to read the RSSI value.

Regards

Marcel

Marcel,

Reading the RSSI by the kernel, will force a certain limitation on the
current and future Profiles. I believe setting the timing should be done
by the profile itself, not the bluez user space code or the kernel. It
is the responsibility of the profile to periodically poll the RSSI Level.
For some cases, polling it every 5 seconds would be ok, and for some
Others, it may be better to read it every second. I believe we must not
impose any limitation here.

You probably forgot that besides bluetoothd there should be no other
application holding the mgmt socket, so not you can't really do it in
poll in the application side and doing it over D-Bus is overkill. Also
I notice that from some parties, you include, there is some tendency
to have the profiles split from the bluetoothd, IMO this will only add
fragmentation with each and every platform using BlueZ having their
own implementation of each profile and not sharing much, making the
IOP a complete mess.


-- 
Luiz Augusto von Dentz