From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 4/6] qmimodem: extract network time from serving system
Date: Fri, 08 Sep 2017 12:20:35 -0500 [thread overview]
Message-ID: <e01f6baf-db46-4de3-d313-26be27c92ca9@gmail.com> (raw)
In-Reply-To: <158bbb77-3391-316c-98e6-ba22f9737c0e@southpole.se>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
Hi Jonas,
>> +
>> + time_3gpp = qmi_result_get(result, QMI_NAS_RESULT_3GPP_TIME, &len);
> And here:
>
> /* Universal Time and Local Time Zone 3GPP */
> time_3gpp = qmi_result_get(result, 0x1c, &len);
>
> (That might be the sound of Denis screaming in the background you hear!
> :) I'm not sure he'll agree with this... we'll see).
>
So generally our preferred approach is not to spend lots of time
defining data structures and #defines that end up being used only once.
They belong directly in the driver code. If you look at the RIL plugin,
that is mostly how things are done, e.g. very much along the lines you
propose.
In the case of QMI, we had plans to have a command line tool that could
interact with QMI devices without running full-blown oFono. So that is
why we placed many of the protocol numbers and structure definitions
into .h files.
For things that are unlikely to go into such a tool, I'm fine with
directly implementing / decoding the data structures inside, but its
hard to determine what might or might not be wanted in such a tool. So
it may be worthwhile to just put all structure definitions into
nas/wds/etc .h for now and make sure that the naming stays sane and
consistent.
Regards,
-Denis
next prev parent reply other threads:[~2017-09-08 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 20:22 [PATCH 1/6] voicecall, common: promote call_status_to_string() to be public Alexander Couzens
2017-09-07 20:22 ` [PATCH 2/6] voicecall: use ofono_call_status_name in DBG messages Alexander Couzens
2017-09-07 20:22 ` [PATCH 3/6] qmimodem: add strength (in %) to the debug output Alexander Couzens
2017-09-07 21:49 ` Denis Kenzior
2017-09-07 20:22 ` [PATCH 4/6] qmimodem: extract network time from serving system Alexander Couzens
2017-09-07 21:50 ` Denis Kenzior
2017-09-08 8:48 ` Jonas Bonn
2017-09-08 9:33 ` Jonas Bonn
2017-09-08 17:20 ` Denis Kenzior [this message]
2017-09-07 20:22 ` [PATCH 5/6] gprs: use registration_status_to_string in debug messages Alexander Couzens
2017-09-07 21:51 ` Denis Kenzior
2017-09-07 20:23 ` [PATCH 6/6] plugins/udevng: use else if instead of if Alexander Couzens
2017-09-07 21:52 ` Denis Kenzior
2017-09-07 21:57 ` [PATCH 1/6] voicecall, common: promote call_status_to_string() to be public Denis Kenzior
2017-09-07 22:27 ` [PATCH][v2 1/2] voicecall, common: move call_status_to_string() to common Alexander Couzens
2017-09-07 22:27 ` [PATCH][v2 2/2] voicecall: use ofono_call_status_name in DBG messages Alexander Couzens
2017-09-07 22:30 ` [PATCH][v2 1/2] voicecall, common: move call_status_to_string() to common 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=e01f6baf-db46-4de3-d313-26be27c92ca9@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