From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCHv2 0/2] CPIN polling mechanism
Date: Fri, 22 Jul 2011 09:18:49 -0500 [thread overview]
Message-ID: <4E2986C9.6020908@gmail.com> (raw)
In-Reply-To: <1311242513-17724-1-git-send-email-nicolas.bertrand@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Hi Nicolas,
On 07/21/2011 05:01 AM, Nicolas Bertrand wrote:
> v2 changes:
> - change AT channel from modem to aux
> - raise timeout to 20 since some dongle take a while to be
> operational
> - send sim inserted notify related to the current status
>
> As no SIM card status urc is available with ZTE and Speedup, the SIM
> state is set by default to OFONO_SIM_STATE_INSERTED even if no SIM card
> is inserted. Also, we are facing with a modem latency after the ttyUSB
> is opened (first AT commands are failing and the PIN status query
> returns CME ERROR: 14 - SIM Busy).
> So, to deal with those 2 issues, this patch set is introducing a
> preliminary PIN status polling in the ZTE/Speedup plugins. In practice,
> this polling is started after the modem is enabled and stopped when the
> CPIN query returns an other result than CME ERROR 14 or when the polling
> duration exceeds 5 seconds.
> As a result, the SIM state is set according the result of the CPIN query
> and the update of the modem_powered state is postponed which delays the
> next AT commands.
>
> Developed conjointly with philippe nunes.
>
I've added PIN polling utility to drivers/atmodem/atutil.c and have made
the mbm plugin use this. Can you check whether this utility is suitable
for ZTE/Speedup drivers?
Regards,
-Denis
prev parent reply other threads:[~2011-07-22 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 10:01 [PATCHv2 0/2] CPIN polling mechanism Nicolas Bertrand
2011-07-21 10:01 ` [PATCHv2 1/2] speedup: add cpin " Nicolas Bertrand
2011-07-21 10:01 ` [PATCHv2 2/2] zte: " Nicolas Bertrand
2011-07-22 14:18 ` 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=4E2986C9.6020908@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.