Re: driver callback naming

[Denis Kenzior <denkenz@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

Hi Aki,

> 2009/8/30 Denis Kenzior <denkenz@gmail.com>:
> > The reason for this is e.g. airplane mode, where you physically want to
> > turn off the device.  Another case is for battery / power reasons, e.g. a
> > netbook with a USB modem that is not being used.
>
> For airplane mode, you want to turn off the radios. I'm also a bit
> unclear where in the Nokia modem API the enable/disable callbacks
> would map. Offline mode can be set via the modem API, but completely
> powering the modem off is done in HW.

Turning off the radio is the intention.  However, oFono is not only to be used 
with proper modems, but with Bluetooth HFP, SAP, etc, where poweroff might have 
different meaning.  Some hardware supports even more drastic powerdown 
procedures than simply turning off the radio.

>
> On a somewhat related note, I don't quite see what to do with
> deregister in the netreg driver. Is the intended end state of the
> device, in fact, similar to airplane mode?

This maps directly to AT+COPS=2, which means completely deregister from 
network, but still be in full-capability mode.  The usefulness of this is of 
course questionable, like many other areas of the spec.  I'm actually willing 
to drop this from the driver, however there might be some use for this 
functionality when using manual operator selection.

Regards,
-Denis