All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aki Niemi <aki@protocolpolice.com>
To: ofono@ofono.org
Subject: Re: [gprs-provision RFCPATCHv6 0/4] Plugin API for provisioning of GPRS context settings
Date: Wed, 26 Jan 2011 12:43:43 +0200	[thread overview]
Message-ID: <AANLkTinWmPRj2J6RPVs__7pm-d9yxO17erggMjm1kY9r@mail.gmail.com> (raw)
In-Reply-To: <1296035821.1520.100.camel@aeonflux>

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

Hi Marcel,

2011/1/26 Marcel Holtmann <marcel@holtmann.org>:
> lets get this merged without support for SPN for now. We can easily add
> this later. So please fix Denis' comments and re-submit this without the
> SPN change.
>
> Andrew is currently looking into fixing the SIM reading race. Once that
> is done we can tackle the SPN part. Feel free to add a TODO item for
> adding access to SPN information.

By SIM race do you mean an atom getting removed while it has a pending
ofono_sim_read?

> Right now I think we need to do that in the SIM atom, store it, and then
> provide it for netreg and other plugins that might want it. However we
> might need to discuss this a bit further.

I think this is actually easy to fix internally to the sim atom. The
first ofono_sim_read() to EFspn would initiate an async read, and any
call to ofono_sim_read() after the fact would pend on that single read
results, or return immediately with cached results if available.

There is still the SIM race problem, but I would really rather solve
that problem by always having all atoms created and removed in the
same callbacks, without returning to mainloop.
Whether atoms register any D-Bus API in certain modem states is then a
different matter.

But the lifetime of all atoms should be the same, and then the SIM
race is again a local matter to the SIM atom to fix. E.g., cancelling
any pending reads it has on the SIM when it gets removed. Simply
removing the driver should take care of this, in fact (at least
isimodem should handle such a thing gracefully).

So I don't see the point in removing the SPN code from provisioning
right now. It is a necessary part of the solution, so at least we need
to keep the task open as long as SPN is not in.

Cheers,
Aki

  reply	other threads:[~2011-01-26 10:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 12:15 [gprs-provision RFCPATCHv6 0/4] Plugin API for provisioning of GPRS context settings Jukka Saunamaki
2011-01-25 12:15 ` [PATCH 1/4] gprs-provision: add driver API header Jukka Saunamaki
2011-01-25 20:59   ` Denis Kenzior
2011-01-25 12:15 ` [PATCH 2/4] gprs-provision: add driver API sources Jukka Saunamaki
2011-01-25 12:15 ` [PATCH 3/4] gprs: add gprs context provisioning Jukka Saunamaki
2011-01-25 21:08   ` Denis Kenzior
2011-01-25 12:15 ` [PATCH 4/4] gprs-provision: add example context provisioning driver Jukka Saunamaki
2011-01-25 12:28 ` [gprs-provision RFCPATCHv6 0/4] Plugin API for provisioning of GPRS context settings Marcel Holtmann
2011-01-25 12:47   ` Jukka Saunamaki
2011-01-26  9:57     ` Marcel Holtmann
2011-01-26 10:43       ` Aki Niemi [this message]
2011-01-26 11:18         ` Marcel Holtmann

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=AANLkTinWmPRj2J6RPVs__7pm-d9yxO17erggMjm1kY9r@mail.gmail.com \
    --to=aki@protocolpolice.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.