Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] telit: sim status notification without polling
Date: Thu, 23 Aug 2012 09:21:33 -0500	[thread overview]
Message-ID: <50363C6D.3090509@gmail.com> (raw)
In-Reply-To: <1345645446-3387-2-git-send-email-christopher.vogl@hale.at>

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

Hi Christopher,

On 08/22/2012 09:24 AM, Christopher Vogl wrote:
> Use AT#QSS=2 instead of AT#QSS=1 to get an URC when the SIM is not only
> inserted but also when PIN is unlocked and when SMS + phonebook are
> ready to be used.
>
> Disable sim state notification in telit_enable() so that we sure get a
> notification when we enable it later again. This way we don't have to
> query the state the first time. Without this the Telit modem does not
> always send an URC when AT#QSS=2 is sent.
>
> Remove sim_inserted_source and sim_inserted_timeout_cb which are not
> needed anymore as a consequence.
> By the way the 1 second timeout was an ugly hack.
>
> Don't query current SIM status in cfun_enable_cb() as the SIM is
> disabled due to prior AT+CFUN=4.
>
> Register '#QSS:' before enabling sim state notifications.
>
> Remove telit_qss_cb() which was used as a callback for querying the
> current SIM status.
> ---
>   plugins/telit.c |   96 +++++++++++++++++++-----------------------------------
>   1 files changed, 34 insertions(+), 62 deletions(-)
>

Patch looks good to me overall, however:

cc1: warnings being treated as errors
plugins/telit.c: In function ‘switch_sim_state_status’:
plugins/telit.c:226:4: error: statement with no effect
plugins/telit.c:240:4: error: statement with no effect
plugins/telit.c: At top level:
plugins/telit.c:64:20: error: ‘qss_prefix’ defined but not used

Also, one other thing I'm concerned about is the CFUN=4 usage when we 
try to set the modem offline.  Your comments indicate that the Telit 
modem resets the SIM when we issue CFUN=4.  Going from Online True -> 
False we don't actually want to reset the SIM.  Does CFUN take an extra 
parameter to turn SIM reset off by any chance?

Regards,
-Denis

  reply	other threads:[~2012-08-23 14:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 13:16 [PATCH 1/8] telit: notify sim inserted when sim ready Christopher Vogl
2012-08-13 13:23 ` Denis Kenzior
2012-08-20 14:34   ` Christopher Vogl
2012-08-20 14:50     ` Denis Kenzior
2012-08-20 15:20       ` Christopher Vogl
2012-08-20 15:42         ` Denis Kenzior
2012-08-22 14:24           ` [PATCH] sim: return from CPIN when SIM unlocked for telit Christopher Vogl
2012-08-22 14:24             ` [PATCH] telit: sim status notification without polling Christopher Vogl
2012-08-23 14:21               ` Denis Kenzior [this message]
2012-08-23 16:00                 ` Christopher Vogl
2012-08-23 17:37                   ` Denis Kenzior
2012-08-24 10:26                     ` Christopher Vogl
2012-08-28 15:19                     ` Christopher Vogl
2012-08-28 14:53                       ` Denis Kenzior
2012-08-29 15:01                         ` [PATCH] telit: enable extended sim status notification Christopher Vogl
2012-08-30 14:46                           ` Denis Kenzior
2012-08-22 23:44             ` [PATCH] sim: return from CPIN when SIM unlocked for telit Denis Kenzior

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=50363C6D.3090509@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox