Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/2] cinterion: Add cinterion vendor support
Date: Fri, 01 May 2015 09:02:28 -0500	[thread overview]
Message-ID: <55438774.9010904@gmail.com> (raw)
In-Reply-To: <1430420897-31084-1-git-send-email-ajlennon@dynamicdevices.co.uk>

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

Hi Alex,

On 04/30/2015 02:08 PM, Alex J Lennon wrote:
> Implement OFONO_VENDOR_CINTERION specific support to register
> textual +CIEV indications for signal strength using vendor
> specific AT^SIND command
> ---
>   drivers/atmodem/network-registration.c | 64 ++++++++++++++++++++++++++++++++--
>   drivers/atmodem/vendor.h               |  1 +
>   2 files changed, 62 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/atmodem/network-registration.c b/drivers/atmodem/network-registration.c
> index a438726..c3507cc 100644
> --- a/drivers/atmodem/network-registration.c
> +++ b/drivers/atmodem/network-registration.c
> @@ -838,6 +838,39 @@ static void telit_ciev_notify(GAtResult *result, gpointer user_data)
>   	ofono_netreg_strength_notify(netreg, strength);
>   }
>
> +static void cinterion_ciev_notify(GAtResult *result, gpointer user_data)
> +{
> +	struct ofono_netreg *netreg = user_data;
> +	struct netreg_data *nd = ofono_netreg_get_data(netreg);
> +	const char *signal_identifier = "rssi";
> +	const char *ind_str;
> +	int strength;
> +	GAtResultIter iter;
> +
> +	g_at_result_iter_init(&iter, result);
> +
> +	if (!g_at_result_iter_next(&iter, "+CIEV:"))
> +		return;
> +
> +	if (!g_at_result_iter_next_unquoted_string(&iter, &ind_str))
> +		return;
> +
> +	if (!g_str_equal(signal_identifier, ind_str))
> +		return;
> +
> +	if (!g_at_result_iter_next_number(&iter, &strength))
> +		return;
> +
> +	DBG("rssi %d", strength);
> +
> +	if (strength == nd->signal_invalid)
> +		strength = -1;
> +	else
> +		strength = (strength * 100) / (nd->signal_max - nd->signal_min);
> +
> +	ofono_netreg_strength_notify(netreg, strength);
> +}
> +
>   static void ctzv_notify(GAtResult *result, gpointer user_data)
>   {
>   	struct ofono_netreg *netreg = user_data;
> @@ -1494,13 +1527,17 @@ static void at_cmer_set_cb(gboolean ok, GAtResult *result, gpointer user_data)
>   	}
>
>   	/*
> -	 * Telit uses strings instead of numbers to identify indicators
> -	 * in a +CIEV URC.
> -	 * Handle them in a separate function to keep the code clean.
> +	 * Telit/Cinterion uses strings instead of numbers to identify
> +	 * indicators in a +CIEV URC.
> +	 * Handle them in separate functions to keep the code clean.
>   	 */

Why is this comment here?  It looks like this function is never called 
in the case of OFONO_VENDOR_CINTERION.  Or am I missing something?

>   	if (nd->vendor == OFONO_VENDOR_TELIT)
>   		g_at_chat_register(nd->chat, "+CIEV:",
>   				telit_ciev_notify, FALSE, netreg, NULL);
> +	else if (nd->vendor == OFONO_VENDOR_CINTERION)
> +	{
> +	  /* +CIEV handling has been registered in at_creg_set_cb() */
> +	}

This part seems to be completely unnecessary?  At least by my reading of 
the code flow, at_cmer_set_cb is never called in the case of 
OFONO_VENDOR_CINTERION.

This is not our coding style.  Please refer to doc/coding-style.txt and 
the Linux Kernel coding style document here: 
https://www.kernel.org/doc/Documentation/CodingStyle.

>   	else
>   		g_at_chat_register(nd->chat, "+CIEV:",
>   				ciev_notify, FALSE, netreg, NULL);
> @@ -1915,6 +1952,27 @@ static void at_creg_set_cb(gboolean ok, GAtResult *result, gpointer user_data)
>   		g_at_chat_send(nd->chat, "AT*TLTS=1", none_prefix,
>   						NULL, NULL, NULL);
>   		break;
> +	case OFONO_VENDOR_CINTERION:
> +		/*
> +		 * We can't set rssi bounds from Cinterion responses
> +		 * so set them up to specified values here
> +		 *
> +		 * Cinterion rssi signal strength specified as:
> +		 * 0      <= -112dBm
> +		 * 1 - 4  signal strengh in 15 dB steps
> +		 * 5      >= -51 dBm
> +		 * 99     not known or undetectable
> +		 */
> +		nd->signal_min = 0;
> +		nd->signal_max = 5;
> +		nd->signal_invalid = 99;
> +
> +		/* Register for specific signal strength reports */
> +		g_at_chat_send(nd->chat, "AT^SIND=\"rssi\",1", none_prefix,
> +				NULL, NULL, NULL);
> +		g_at_chat_register(nd->chat, "+CIEV:",
> +				cinterion_ciev_notify, FALSE, netreg, NULL);
> +		break;
>   	case OFONO_VENDOR_NOKIA:
>   	case OFONO_VENDOR_SAMSUNG:
>   		/* Signal strength reporting via CIND is not supported */
> diff --git a/drivers/atmodem/vendor.h b/drivers/atmodem/vendor.h
> index c132e45..52071c8 100644
> --- a/drivers/atmodem/vendor.h
> +++ b/drivers/atmodem/vendor.h
> @@ -45,4 +45,5 @@ enum ofono_vendor {
>   	OFONO_VENDOR_ALCATEL,
>   	OFONO_VENDOR_QUECTEL,
>   	OFONO_VENDOR_UBLOX,
> +	OFONO_VENDOR_CINTERION,
>   };
>

Regards,
-Denis

  parent reply	other threads:[~2015-05-01 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 19:08 [PATCH 1/2] cinterion: Add cinterion vendor support Alex J Lennon
2015-04-30 19:08 ` [PATCH 2/2] cinterion: Replace tc65 plugin with vendor generic cinterion plugin Alex J Lennon
2015-05-01 14:05   ` Denis Kenzior
2015-05-01 21:11     ` Alex J Lennon
2015-05-01 14:02 ` Denis Kenzior [this message]
2015-05-12 17:27   ` [PATCH 1/2] cinterion: Add cinterion vendor support Alex J Lennon

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=55438774.9010904@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