Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/8] telit: notify sim inserted when sim ready
Date: Mon, 20 Aug 2012 10:42:29 -0500	[thread overview]
Message-ID: <50325AE5.8090502@gmail.com> (raw)
In-Reply-To: <503255A5.7000403@hale.at>

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

Hi Christopher,

On 08/20/2012 10:20 AM, Christopher Vogl wrote:
> Hi Denis,
>
> On 20/08/12 16:50, Denis Kenzior wrote:
>> Hi Christopher,
>>
>> <snip>
>>
>>>>
>>>> You might need to do the same thing as we did for e.g. IFX and STE.
>>>> notify sim insertion on #QSS: 1, and only return from CPIN once #QSS:
>>>> 3 has been sent. See drivers/atmodem/sim.c at_epev_notify() or
>>>> at_xsim_notify() for an example.
>>>
>>> This works fine in case the PIN is locked, but has the unpleasant side
>>> effect that I receive a timeout when calling the D-Bus method to enter
>>> the PIN because #QSS: 3 takes so long (e.g. 32 seconds from entering the
>>> PIN until a #QSS: 3).
>>
>> Feel free to extend the timeout on the enter-pin script. Also, you can
>> in theory wait until #QSS: 2 and not 3 right? From what I remember
>> QSS: 3 pertains to Phonebook and SMS being ready.
> That's right!
>
>> For those you can add a quirk that queries / waits for QSS:3 See how
>> we handled this in plugins/calypso.c and %CSTAT.
> Thanks for the hint! I was thinking about a solution like that but
> thought that I was not ment to move the creation of atoms elsewhere.
>
>> Alternatively we can try to do this inside the individual drivers
>> using a vendor quirk.
> I like the %CSTAT way because I think it is a clean and easy to follow
> solution.
> In that case I also don't have to work with QSS in drivers/atmodem/sim.c
> anymore.
>

Well you might still need to wait for #QSS: 2 in drivers/atmodem/sim.c. 
  Many modems have the nasty habit of returning SIM busy errors when the 
CPIN state is queried right after PIN entry.

Regards,
-Denis

  reply	other threads:[~2012-08-20 15:42 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 [this message]
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
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=50325AE5.8090502@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