From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 5/6] Add a function to be able to report network technology change
Date: Mon, 22 Jul 2013 15:57:49 -0500 [thread overview]
Message-ID: <51ED9CCD.1020508@gmail.com> (raw)
In-Reply-To: <1374240940-30892-5-git-send-email-viallard@syscom-instruments.com>
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
Hi Anthony,
On 07/19/2013 08:35 AM, Anthony Viallard wrote:
> When we detect a change of the network technology, ofono don't have
> a function to report this change at higher level (dbus signal, ...)
> ---
> include/netreg.h | 1 +
> src/network.c | 6 ++++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/include/netreg.h b/include/netreg.h
> index 4338c14..94c8e9f 100644
> --- a/include/netreg.h
> +++ b/include/netreg.h
> @@ -91,6 +91,7 @@ struct ofono_netreg_driver {
> void ofono_netreg_strength_notify(struct ofono_netreg *netreg, int strength);
> void ofono_netreg_status_notify(struct ofono_netreg *netreg, int status,
> int lac, int ci, int tech);
> +void ofono_netreg_tech_notify(struct ofono_netreg *netreg, int tech);
Please don't do this, the tech is already covered by netreg_status_notify
> void ofono_netreg_time_notify(struct ofono_netreg *netreg,
> struct ofono_network_time *info);
>
> diff --git a/src/network.c b/src/network.c
> index d1bfca6..b4cd62f 100644
> --- a/src/network.c
> +++ b/src/network.c
> @@ -1393,6 +1393,12 @@ void ofono_netreg_status_notify(struct ofono_netreg *netreg, int status,
> notify_status_watches(netreg);
> }
>
> +void ofono_netreg_tech_notify(struct ofono_netreg *netreg, int tech)
> +{
> + if (netreg->technology != tech)
> + set_registration_technology(netreg, tech);
> +}
> +
> void ofono_netreg_time_notify(struct ofono_netreg *netreg,
> struct ofono_network_time *info)
> {
>
Regards,
-Denis
next prev parent reply other threads:[~2013-07-22 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 13:35 [PATCH 1/6] Add SIMCOM support Anthony Viallard
2013-07-19 13:35 ` [PATCH 2/6] SIMCOM: add a quirk for AT+CNMI command building Anthony Viallard
2013-07-22 20:49 ` Denis Kenzior
2013-07-19 13:35 ` [PATCH 3/6] SIMCOM: add a quirk for signal strength reporting Anthony Viallard
2013-07-22 20:49 ` Denis Kenzior
2013-07-19 13:35 ` [PATCH 4/6] SIMCOM: add a quirk to fix crsm request Anthony Viallard
2013-07-22 20:51 ` Denis Kenzior
2013-07-19 13:35 ` [PATCH 5/6] Add a function to be able to report network technology change Anthony Viallard
2013-07-22 20:57 ` Denis Kenzior [this message]
2013-07-19 13:35 ` [PATCH 6/6] SIMCOM: add a quirk to retrieve network technology used Anthony Viallard
2013-07-22 21:08 ` Denis Kenzior
2013-07-22 20:45 ` [PATCH 1/6] Add SIMCOM support 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=51ED9CCD.1020508@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