Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sim: showing lock state with call meter
Date: Fri, 25 Feb 2011 11:58:44 -0600	[thread overview]
Message-ID: <4D67EDD4.2040507@gmail.com> (raw)
In-Reply-To: <1298640016-25471-1-git-send-email-jussi.kangas@tieto.com>

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

Hi Jussi,

On 02/25/2011 07:20 AM, Jussi Kangas wrote:
> ---
> 
> Hi,
> 
> Here is the fixed patch for enabling the showing of pin2 blocked 
> situation in SIM API when lock state changes after using call meter
> API.
> 
> Br,
> Jussi 
> 
>  include/sim.h    |    2 ++
>  src/call-meter.c |   19 +++++++++++++++++++
>  src/sim.c        |   46 +++++++++++++++++++++++++++++++---------------
>  3 files changed, 52 insertions(+), 15 deletions(-)
> 

I applied this patch, but broke it up into three separate commits:

9007bf63927b7008129a7704a8fd0649fed67065
c5b321e768a9f36ba55dc9ce39d8f28c527a57eb
07c7308581c921ad1ff70903c8534ac01e62b549

Few more comments below:

>  
>  checkdone:
> -	if (pin_type == OFONO_SIM_PASSWORD_NONE)
> +	switch (pin_type) {
> +	case OFONO_SIM_PASSWORD_SIM_PIN2:
> +	case OFONO_SIM_PASSWORD_SIM_PUK2:
> +		if (sim->state == OFONO_SIM_STATE_READY)
> +			break;
> +	case OFONO_SIM_PASSWORD_NONE:
>  		sim_initialize_after_pin(sim);
> +		break;

If we correctly enter PIN2 or unblock PIN2, do we go back to the READY
state?  If so, we might want to avoid running the initialization
procedure above.

> +	default:
> +		break;
> +	}
>  }

Regards,
-Denis

  reply	other threads:[~2011-02-25 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 13:20 [PATCH] sim: showing lock state with call meter Jussi Kangas
2011-02-25 17:58 ` Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-22 12:05 Jussi Kangas
2011-02-23  6:15 ` Denis Kenzior
2011-02-23 15:24   ` Jussi Kangas
2011-02-24 20:17     ` Denis Kenzior
2011-02-25 13:19       ` Jussi Kangas
2011-02-25 17:07         ` 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=4D67EDD4.2040507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox