All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Access to SIM card when Modem is not "Powered"
Date: Tue, 30 Mar 2010 11:13:35 -0500	[thread overview]
Message-ID: <201003301113.36166.denkenz@gmail.com> (raw)
In-Reply-To: <80fd4e751003300834t57552977r2355e01810ff8964@mail.gmail.com>

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

Hi Pekka,

> Sure.
> 
> I want Powered-1 that controls the atoms. Atoms should be loaded when
> modem is in responsive state and removed when, e.g., modem reboots.
> This we can do now, iow, if you connect a Nokia phone via USB, oFono
> can follow its state via the MTC indications it sends on top of the
> phonet link running over USB.
> 
> I want Powered-2 that controls the modem power. When ofonod starts in
> N900, it should power up the internal modem. When ofonod terminates
> itself, it should shut down modem nicely before calling exit().

So I think I finally understood.  What you're trying to achieve is modem 
presence detection / removal.  The equivalent of what udev / modemconf plugins 
do for oFono.  Except that your modem is always present and you need to power 
it up / down.

The answer is that exposing this as a property is not going to happen because 
it is fundamentally wrong.  And in effect it already is exposed, e.g. the fact 
that modem object is present in oFono.  You have several options here:

- Create an oFono plugin to listen to an external daemon and create/destroy 
the modem object appropriately
- Create an oFono plugin that will replace the external daemon and 
create/destroy the modem object appropriately
- Implement this properly in the kernel driver and signal device presence via 
netlink / udev / etc

Regards,
-Denis

  parent reply	other threads:[~2010-03-30 16:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 17:24 Access to SIM card when Modem is not "Powered" Pekka Pessi
2010-03-19 18:18 ` Denis Kenzior
2010-03-29 18:29   ` Pekka Pessi
2010-03-29 18:40     ` Bastian, Waldo
2010-03-30 11:39       ` Pekka Pessi
2010-03-30 14:22         ` Marcel Holtmann
2010-03-29 18:53     ` Denis Kenzior
2010-03-30 11:36       ` Pekka Pessi
2010-03-30  4:50         ` Denis Kenzior
2010-03-30 15:34           ` Pekka Pessi
2010-03-30 15:45             ` Marcel Holtmann
2010-03-30 16:40               ` Pekka Pessi
2010-03-30 18:02                 ` Marcel Holtmann
2010-03-30 22:55                   ` Pekka Pessi
2010-03-30 23:24                     ` Denis Kenzior
2010-04-01  9:14                       ` Pekka Pessi
2010-04-01 12:44                         ` Aki Niemi
2010-04-01 15:09                           ` Denis Kenzior
2010-04-01 15:07                         ` Denis Kenzior
2010-04-12 14:08                           ` Pekka Pessi
2010-04-15 21:54                             ` Denis Kenzior
2010-03-30 17:26               ` Aki Niemi
2010-03-30 16:13             ` Denis Kenzior [this message]
2010-03-30 17:37               ` Aki Niemi
2010-03-30 18:05                 ` Denis Kenzior
2010-03-30 18:27                   ` Aki Niemi
2010-03-30 11:57         ` Aki Niemi
2010-03-30 14:19           ` 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=201003301113.36166.denkenz@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.