From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Fix modem doesn't auto register to network issue
Date: Thu, 12 Sep 2013 08:43:40 -0500 [thread overview]
Message-ID: <5231C50C.1070704@gmail.com> (raw)
In-Reply-To: <DA62CA5DDF4CA640AA25B1684E5D141101D86039@SHSMSX102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
Hi Caiwen,
On 09/11/2013 09:48 PM, Zhang, Caiwen wrote:
> Hi Denis,
>
>>> Some modem may return registration status whitch is out of the range
>>> (0-5). it will cause the modem don't auto register to network when
>>> network atom initializes.
>>
>> oFono core will not validate values outside what is defined in 27.007.
>> If your driver reports such values, then it is an obvious bug in the driver.
>>
>> Please fix your modem driver.
>>
>
> (status == NETWORK_REGISTRATION_STATUS_NOT_REGISTERED ||
> status == NETWORK_REGISTRATION_STATUS_DENIED ||
> status == NETWORK_REGISTRATION_STATUS_UNKNOWN)
>
> Above checking tries to list the cases that should trigger auto network registration but for the modems which
> extend network registration status may miss some cases.
>
> With the new checking:
> (status != NETWORK_REGISTRATION_STATUS_REGISTERED &&
> status != NETWORK_REGISTRATION_STATUS_SEARCHING &&
> status != NETWORK_REGISTRATION_STATUS_ROAMING))
> it tries to exclude the cases that not required to trigger auto network registration. In this way, it can avoid
> above issue.
Since we do not know what the meaning of the extended value actually is,
we can be wrong in either situation. The core only knows about values
defined in 27.007 or values it defines explicitly inside include/*. If
we start having the core deal with every single vendor extension then we
will quickly go insane and the core becomes unreadable.
I have been and will continue to be quite adamant here. Fix. Your. Driver.
>
> I am not sure whether other modem has the same issue. This way should be more make sense.
>
> By the way, it should be better to change the status from "int" to " enum network_registration_status" to avoid modem driver pass
> in value we don't expect.
How does this help you? If your modem reports issues outside the range,
you still need to sanitize the values you send to the core. If your
modem is compliant, then converting them to an enum just leads to you
writing more code that does nothing useful.
We've tried this already and abandoned it long ago.
Regards,
-Denis
prev parent reply other threads:[~2013-09-12 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 17:33 [PATCH] Fix modem doesn't auto register to network issue caiwen.zhang
2013-09-11 17:43 ` Denis Kenzior
2013-09-12 2:48 ` Zhang, Caiwen
2013-09-12 13:43 ` Denis Kenzior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5231C50C.1070704@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.