Hi Zhengguang, On Wed, Jun 01, 2011 at 03:52:23AM -0400, [email protected] wrote: > From: zzhang0 <[email protected]> > > In current connman implementation, when we turn on/off airplane mode > quickly, sometimes, it may lead to device status conflict. > For example, initial status is airplane mode off, bluetooth device on, > then when we turn on/off airplane mode qucikly, bluetooth device will be > enabled and disabled according to it. But the bluetooth enable/disable > operation is asynchronous, in some time, for example if the device is in > the progress of powering on but not powered completed yet, then turn on > airplane mode, which means to disable the bluetooth device, connman will > treat it as the same device status and ignore the operation, > then the status would be turned to airplane mode on, bluetooth device on, > which can't keep consistent with the initial status. > > This patch is trying to fix this issue, and the solution is when the device > is in powering progress, forbid upper layer to call manager dbus interface > to set "OfflineMode" properity. Thanks a lot for looking into this one. The problem I see here is that we shouldn't prevent the user from turning offline mode on because an operation is in progress. If you get an offline mode request, you can either cancel all pending power operations, or wait for them to complete and then set the offline mode. But having the user toggling the offline mode switch twice because a power operations is pending is not acceptable.
Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
