Re: [RFC BlueZ]Proximity Monitor: Immediate Alert Timeout

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Hemant,

On Wed, Dec 14, 2011 at 10:18 AM, Hemant Gupta
<hemantgupta.ste@xxxxxxxxx> wrote:
> Hi,
>
> I am working on Proximity Monitor Role using BlueZ 4.96 + and have a
> query on the need for Timeout in case of Immediate Alert in file
> proximity/monitor.c.
>
> I feel that this timer is not required, because this will lead to
> following scenario in case of Proximity Profile:
>
> If Path loss has occurred and Immediate Alert has been written, then
> after Timeout (5 seconds), Proximity Monitor will set immediate alert
> level to “none”, which will indicate to Proximity Reporter that Path
> Loss is now within threshold, which actually might not be the case.

I think this timeout is causing more harm than good (sometimes due to
temporary latency between the two writes, the "none" alert level may
arrive right after the previous level, which may cause the reporter to
remain silent), so I agree with you. But I will wait for Claudio's
opinion as he implemented this timeout in the first place :)

> As per Sec 4.6 of Proximity Profile Spec,
> “If the path loss falls below a threshold set on the Proximity Monitor
> it shall write in the Alert Level characteristic of the Immediate
> Alert service, using the GATT Write Without Response sub-procedure, to
> cause the Proximity Reporter to end the alert. When the path loss is
> below the threshold the Proximity Monitor should stop alerting.”
>
> So this means that the proximity monitor should not change the alert
> level to “None” until the path loss is above Threshold.

I think it is better to not have BlueZ itself change the alert level
to "none", instead the application can do this when it detects the
path loss above Threshold. This can be easily achieved by monitoring
the "SignalLevel" property changes on the Proximity API, and writing
to ImmediateAlertLevel as necessary. After all, the threshold is
dependent on the application settings.

Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia - 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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux