From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] rilmodem: Fix GPRS feature inavailable issue
Date: Thu, 14 Jan 2016 09:52:35 -0600 [thread overview]
Message-ID: <5697C443.7090609@gmail.com> (raw)
In-Reply-To: <DA62CA5DDF4CA640AA25B1684E5D141102069F97@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Hi Caiwen,
Please don't top-post on this list. Thanks for your understanding.
Now as to your question:
>
> In fact I have ever considered the way you mentioned. But l found in most plugins, atoms (gprs, gprs_context, sms,
> call_forwarding ...) are created at post_sim phrase. It seems post_online phrase is more reasonable. There should
> be some reason that the atom creation is brought forward. Does anyone know the reason?
>
It really depends on what the particular atom supports and what the
hardware supports. The modem driver has some leeway to place atoms in
the appropriate state callback (.pre_sim, .post_sim, .post_online).
Generally, anything that accesses the SIM can safely go into .post_sim
if the hardware supports this mode properly, e.g. sim on, rx/tx radio
circuits off. sim and gprs atoms also support being in post_sim. This
is done so that settings can be tweaked while offline.
In the case of the rilmodem gprs driver, the querying of max_cids is
needed in order to tell oFono core the id range. This operation needs
to be done once before the atom is registered. If this operation is not
available on the RIL in 'post_sim' (not online) state, then it is safer
to move the gprs atom into post_online callback than trying to follow
radio state changes and (repeatedly) query max_cids.
If you really need gprs to be in post_sim, then we can discuss some
alternative solutions.
Regards,
-Denis
next prev parent reply other threads:[~2016-01-14 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 3:42 [PATCH] rilmodem: Fix GPRS feature inavailable issue caiwen.zhang
2016-01-13 21:10 ` Tony Espy
2016-01-14 6:14 ` Zhang, Caiwen
2016-01-14 15:52 ` Denis Kenzior [this message]
2016-01-14 18:52 ` Tony Espy
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=5697C443.7090609@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.