[PATCH] telit: enable 'SIM ready' notifications with #QSS=2
Carlo Lobrano
c.lobrano at gmail.com
Fri Mar 17 09:35:47 UTC 2017
In this test it took 35 seconds (I was testing 5 seconds timeout here, with
some more debug logs), but I think it's SIM's content dependent
mar 17 09:07:10 D2040 ModemManager[23597]: Waiting up to 5 seconds for SIM
readiness (#QSS: 3)
mar 17 09:07:15 D2040 ModemManager[23597]: After SIM unlock: SIM readiness
timeout 5 expired. Continuing...
mar 17 09:07:18 D2040 ModemManager[23597]: Modem
/org/freedesktop/ModemManager1/Modem/0: state changed (enabling ->
registered)
mar 17 09:07:45 D2040 ModemManager[23597]: (ttyACM3): <-- '#QSS: 3'
On Fri, 17 Mar 2017 at 10:26 Aleksander Morgado <aleksander at aleksander.es>
wrote:
> On Fri, Mar 17, 2017 at 10:23 AM, Carlo Lobrano <c.lobrano at gmail.com>
> wrote:
> >
> > I tested your patch and it seems working fine, even if #QSS: 3 always
> > arrives very late respect any acceptable timeout (the modem reads all SIM
> > values, even sms, before signaling QSS:3).
> > Moreover, this change would be really helpful for the issue I reported in
> > "[PATCH] telit: lock/unlock CSIM operations by default" thread. I'm
> about to
> > write another email about that, because I need some help there.
>
> So, the "#QSS: 3" arrives way after the 1s timeout we added? how much
> after? Would it make sense to wait for #QSS: 3 and if not arrived,
> timeout with a longer value?
>
>
> --
> Aleksander
> https://aleksander.es
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20170317/1b695987/attachment.html>
More information about the ModemManager-devel
mailing list