From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: SAGEM HiloNC v2 Driver
Date: Wed, 27 Mar 2013 14:54:46 -0500 [thread overview]
Message-ID: <51534E86.1040101@gmail.com> (raw)
In-Reply-To: <CAAs3wMjfWfeog=+ECLZZjYEMwNL6nh4fn=phARSwVs06dt9u5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]
Hi Marco,
>
> enable -> pre_sim, sim_inserted -> post_sim, set_online ->
> post_online. Generally you do not call set_online before hitting
> the post_sim state.
>
>
> could I don't implement set_online if I don't need it?
That would work, if the modem driver does not implement set_online,
oFono core automatically transitions to Online after CPIN returns 'READY'.
>
> <snip>
>
>
>
> I've managing vendor URC for sim detection right now but i have
> problems.For instance if I remove it when ofonod is ready the Hilonc
> sends an URC to notify sim status changed but after that it reboots
> itself(2 sec later)... what i did is to notify the stack that
> the SIM
> has been removed and modem is powered off . I thought that after
> calling
> set_powered fnc the stack should have called my driver virtual
> disable
> function in order to properly close the MUX .. but it's not..
>
>
> No, if you call ofono_modem_set_powered(modem, FALSE) it assumes
> that the modem powered off due to an internally generated event
> (e.g. not oFono's doing). The driver has to clean up properly in
> this case. The driver disable() method is only called on oFono
> initiated power down requests.
>
>
> mmh ok..so If the modem restarts it's my business to disable and enable
> again all the driver' stuff , right?
>
If the modem resets, then yes you need to call ofono_modem_set_powered
to FALSE. Booting it back up should not be done in the driver, unless
your modem supports so called silent resets. This is where the modem
stack crashes but silently resets itself back to the previous state.
(e.g. no PIN entry is required, initialization is very fast). In that
case use ofono_modem_reset.
<snip>
Glad I could help ;)
Regards,
-Denis
next prev parent reply other threads:[~2013-03-27 19:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAs3wMjcs_Y6-zFVUX2k8uO6_3tV0CLga2Pty0Cb2M9YOf7_xQ@mail.gmail.com>
2013-03-27 6:29 ` SAGEM HiloNC v2 Driver Freedreamer
2013-03-27 14:36 ` Denis Kenzior
2013-03-27 18:06 ` Freedreamer
2013-03-27 19:54 ` Denis Kenzior [this message]
2013-03-28 13:40 ` Freedreamer
2013-03-28 13:43 ` Freedreamer
2013-03-28 14:28 ` Denis Kenzior
2013-03-28 15:42 ` Freedreamer
2013-03-28 16:04 ` Denis Kenzior
2013-03-28 16:32 ` Freedreamer
2013-03-28 19:41 ` Denis Kenzior
2013-03-29 11:24 ` Freedreamer
2013-04-04 12:08 ` Freedreamer
2013-04-04 13:36 ` Denis Kenzior
2013-04-04 17:18 ` Freedreamer
2013-03-26 9:07 Freedreamer
2013-03-26 14:25 ` 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=51534E86.1040101@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.