From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] plugins/ril: complete modem power off process
Date: Fri, 13 May 2016 20:57:51 -0500 [thread overview]
Message-ID: <5736861F.6000504@gmail.com> (raw)
In-Reply-To: <1463032263-6366-1-git-send-email-caiwen.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
Hi Caiwen,
On 05/12/2016 12:51 AM, caiwen.zhang(a)intel.com wrote:
> From: caiwen Zhang <caiwen.zhang@intel.com>
>
> ---
> plugins/ril.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
I went ahead and applied this patch, however, see below:
> diff --git a/plugins/ril.c b/plugins/ril.c
> index 2298bb6..2ea3fb5 100644
> --- a/plugins/ril.c
> +++ b/plugins/ril.c
> @@ -409,15 +409,30 @@ int ril_enable(struct ofono_modem *modem)
> return -EINPROGRESS;
> }
>
> +static void power_off_cb(struct ril_msg *message, gpointer user_data)
> +{
> + struct cb_data *cbd = user_data;
> + struct ril_data *rd = cbd->user;
> + struct ofono_modem *modem = cbd->data;
> +
> + if (rd) {
> + g_ril_unref(rd->ril);
It seems GRil doesn't gracefully handle g_ril_unrefs from within a
result callback. Have you tried running this with valgrind?
We might need to come up with a fix for GRil...
> + rd->ril = NULL;
> + }
> +
> + ofono_modem_set_powered(modem, FALSE);
> +}
> +
> int ril_disable(struct ofono_modem *modem)
> {
> struct ril_data *rd = ofono_modem_get_data(modem);
> + struct cb_data *cbd = cb_data_new(NULL, modem, rd);
>
> DBG("%p", modem);
>
> - ril_send_power(rd, FALSE, NULL, NULL);
> + ril_send_power(rd, FALSE, power_off_cb, cbd);
>
> - return 0;
> + return -EINPROGRESS;
> }
>
> static struct ofono_modem_driver ril_driver = {
>
Regards,
-Denis
next prev parent reply other threads:[~2016-05-14 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 5:51 [PATCH] plugins/ril: complete modem power off process caiwen.zhang
2016-05-14 1:57 ` Denis Kenzior [this message]
2016-05-16 6:41 ` Zhang, Caiwen
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=5736861F.6000504@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