From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH v2] ifx: Adding modem selftest to Infineon modem
Date: Sat, 18 Dec 2010 19:25:39 +0100 [thread overview]
Message-ID: <1292696739.2658.10.camel@aeonflux> (raw)
In-Reply-To: <1292637119-9288-1-git-send-email-robertino.benis@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
Hi Robertino,
> diff --git a/plugins/ifx.c b/plugins/ifx.c
> index 2f4c65b..3647dbc 100644
> --- a/plugins/ifx.c
> +++ b/plugins/ifx.c
> @@ -71,6 +71,8 @@
> #define GPRS3_DLC 4
> #define AUX_DLC 5
>
> +#define IFX_SELF_TESTS_TIMEOUT 5
> +
this is not what I meant actually. Adding a comment for the
g_timeout_add_seconds is just fine.
What I wanted to know is where the actual value came from. Is 5 seconds
enough? How do we know the time a test takes?
> static char *dlc_prefixes[NUM_DLC] = { "Voice: ", "Net: ", "GPRS1: ",
> "GPRS2: ", "GPRS3: ", "Aux: " };
>
> @@ -80,6 +82,18 @@ static const char *dlc_nodes[NUM_DLC] = { "/dev/ttyGSM1", "/dev/ttyGSM2",
>
> static const char *none_prefix[] = { NULL };
> static const char *xdrv_prefix[] = { "+XDRV:", NULL };
> +static const char *empty_prefix[] = { "", NULL };
This is still wrong. See my comment from the original email. I am not
sure you really know what { "", NULL } means.
> +struct ifx_self_tests {
> + char *test_desc;
> + char *at_cmd;
> +};
> +
> +static const struct ifx_self_tests mst[] = {
> + { "RTC GTI Test", "at(a)rtc:rtc_gti_test_verify_32khz()" },
> + { "Device Version Test", "at(a)vers:device_version_id()" },
> + { NULL, NULL }
> +};
No need to declare the struct before assigning it. Just do it all in
once. And fix up the indentation for the values. Just one tab please.
> struct ifx_data {
> GIOChannel *device;
> @@ -99,6 +113,8 @@ struct ifx_data {
> int audio_loopback;
> struct ofono_sim *sim;
> gboolean have_sim;
> + guint self_test_timeout;
> + int self_test_idx;
> };
>
> static void ifx_debug(const char *str, void *user_data)
> @@ -545,6 +561,64 @@ static gboolean mux_timeout_cb(gpointer user_data)
> return FALSE;
> }
>
> +static gboolean self_test_timeout_cb(gpointer user_data)
> +{
> + struct ofono_modem *modem = user_data;
> + struct ifx_data *data = ofono_modem_get_data(modem);
> +
> + ofono_error("Modem %s: TIMED OUT",
> + mst[data->self_test_idx].test_desc);
> +
> + g_source_remove(data->self_test_timeout);
> + data->self_test_timeout = 0;
> +
> + shutdown_device(data);
> + ofono_modem_set_powered(modem, FALSE);
> +
> + return FALSE;
> +}
I am stopping right here now actually. Please fix my review comments
from the initial review as well. This function is still broken.
Regards
Marcel
next prev parent reply other threads:[~2010-12-18 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 1:51 [PATCH v2] ifx: Adding modem selftest to Infineon modem Robertino Benis
2010-12-18 18:25 ` Marcel Holtmann [this message]
2010-12-18 19:58 ` Bastian, Waldo
2010-12-18 20:48 ` 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=1292696739.2658.10.camel@aeonflux \
--to=marcel@holtmann.org \
--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