All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Bonn <jonas@southpole.se>
To: ofono@ofono.org
Subject: Re: [PATCH 5/8] lte: activate default bearer on network registration
Date: Fri, 14 Apr 2017 23:53:13 +0200	[thread overview]
Message-ID: <3d6e046c-0b3b-5755-9d14-1755fe99338b@southpole.se> (raw)
In-Reply-To: <1a742fa1-e303-3810-60ae-18a5c1bf1770@gmail.com>

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

Hi Denis,

On 04/13/2017 05:14 PM, Denis Kenzior wrote:
> I haven't tested this, but I suspect that calling "Start network" for
>>> the same profile again will fail...??? A profile number corresponds
>>> to a Context ID...???  Maybe...
>>
>
> I would imagine that a profile has the same meaning as the 27.007 
> equivalent of +CGDCONT <cid>

Yes, it does.  Others have tested modifying context parameters with AT 
commands and the changes are visible in the corresponding QMI profile.  
However, this could theoretically be firmware dependent as it's not 
actually specified anywhere that it must be so.

>
>> I tested this and "start network" fails when attempting to connect a
>> profile a second time.
>>
>
> Makes sense.  Do note that the same APN can be (in theory) double, 
> triple, etc activated.  But this requires a separate cid for each 
> instance.

Yes, exactly.  Multiple profiles with identical parameters can be 
activated, as far as I can tell.
>>> Given all of the above, for QMI this means:
>>>
>>> i)  When the netreg atom detects registration to an LTE network then
>>> we can call "Start network" immediately.
>
> gprs atom driver needs to tell ofono core that a context is active. 
> This means gprs driver should call ofono_gprs_cid_activated
>
>>> ii)  Start network will give us the packet-handle for the default
>>> bearer.  This can be held by the netreg atom.
>
> why netreg atom?  This should be managed by gprs-context.

Yes, you're right.  I also came to this insight after writing this email! :)

I originally implemented this as described above but have now posted a 
new series that works as you described.  It really hasn't been easy to 
understand how this all was supposed to work but what I've got now seems 
reasonable and functions well.

One question:  ofono_gprs_notify_bearer()... why do we need this when 
netreg already provides the technology to the GPRS atom?

Thanks for taking the time to help me work through all of this! Much 
appreciated.

/Jonas

  reply	other threads:[~2017-04-14 21:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  8:18 [PATCH lte 0/8] QMI LTE series Jonas Bonn
2017-04-11  8:18 ` [PATCH 1/8] qmi: NAS definitions adjustment Jonas Bonn
2017-04-11 15:23   ` Denis Kenzior
2017-04-11  8:18 ` [PATCH 2/8] qmi: add WDS parameter definition Jonas Bonn
2017-04-11 16:23   ` Denis Kenzior
2017-04-11  8:18 ` [PATCH 3/8] qmi: retrieve GPRS context parameters Jonas Bonn
2017-04-11 16:44   ` Denis Kenzior
2017-04-11  8:18 ` [PATCH 4/8] qmi: implement read_settings for automatic contexts Jonas Bonn
2017-04-11 17:02   ` Denis Kenzior
2017-04-11  8:18 ` [PATCH 5/8] lte: activate default bearer on network registration Jonas Bonn
2017-04-11 17:07   ` Denis Kenzior
2017-04-11 20:48     ` Jonas Bonn
2017-04-11 21:21       ` Denis Kenzior
2017-04-12 14:28         ` Jonas Bonn
2017-04-12 21:10           ` Jonas Bonn
2017-04-13 15:14             ` Denis Kenzior
2017-04-14 21:53               ` Jonas Bonn [this message]
2017-04-14 23:18                 ` Denis Kenzior
2017-04-11  8:18 ` [PATCH 6/8] qmi: add LTE atom driver Jonas Bonn
2017-04-11 17:09   ` Denis Kenzior
2017-04-11  8:18 ` [PATCH 7/8] qmi: watch for automatic context activation Jonas Bonn
2017-04-11  8:18 ` [PATCH 8/8] gobi: add LTE atom Jonas Bonn

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=3d6e046c-0b3b-5755-9d14-1755fe99338b@southpole.se \
    --to=jonas@southpole.se \
    --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.