[PATCH] mbm: don't try to load generic supported modes

[Dan Williams]

On Wed, 2015-12-16 at 17:58 +0100, Aleksander Morgado wrote:
> On Wed, Dec 16, 2015 at 5:55 PM, Dan Williams <dcbw at redhat.com>
> wrote:
> > On Wed, 2015-12-16 at 10:27 +0100, Aleksander Morgado wrote:
> > > We were trying to load the generic modes supported reported by
> > > either
> > > *CNTI=2 or
> > > AT+WS46=?, so that then we could filter out the MBM-specific
> > > modes
> > > unsupported.
> > > 
> > > But, this may not be ideal, as both these two commands may fail:
> > 
> > Sounds fine, and both fail on my MD300 with and without a SIM. 
> >  Perhaps
> > instead we could use +CFUN=? and parse the result:
> > 
> > at+cfun=?
> > +CFUN: (0,1,4-6)
> > 
> > If we get '6' we know it supports 3G.  Even my 2007 era
> > SonyEricsson TM
> > -506 which uses mostly the same command set and supports UMTS says:
> > 
> > at+cfun=?
> > +CFUN: (0,1,4-6),(0,1)
> 
> Now that you checked it; is the CFUN value changed instantly once you
> e.g. switch to 3G-only? Tore was trying this today and he saw that
> after CFUN=6 the modem went to low-power mode  (CFUN=4); pretty 
> weird.

On my MD300 the value is changed immediately once the +CFUN=X returns
(which can take a couple seconds, it seems).  For Tore's, did the modem
come out of LPM and into 6 eventually?  Or stay in LPM?  I wouldn't be
surprised if LPM was part of the cycle if they have to
reboot/reinitialize some of the radio blocks or something.

Dan