From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 6/9] doc: add lte atom documentation
Date: Wed, 09 Nov 2016 14:41:04 -0600 [thread overview]
Message-ID: <582389E0.3070309@gmail.com> (raw)
In-Reply-To: <1478713402-30780-7-git-send-email-dragos@endocode.com>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
Hi Dragos,
On 11/09/2016 11:43 AM, Dragos Tatulea wrote:
> ---
> doc/lte-api.txt | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 doc/lte-api.txt
>
> diff --git a/doc/lte-api.txt b/doc/lte-api.txt
> new file mode 100644
> index 0000000..dfefaf4
> --- /dev/null
> +++ b/doc/lte-api.txt
> @@ -0,0 +1,35 @@
> +LTE Hierarchy
> +
> +Service org.ofono
> +Interface org.ofono.LTE
So oFono tries not to use abbreviations in its API. How about we simply
name this LongTermEvolution
> +Object path [variable prefix]/{modem0,modem1,...}
> +
> +
> +Methods dict GetProperties()
> +
> + Returns all LTE configuration properties.
> +
> + void SetProperty(string property, variant value)
> +
> + Changes the value of the specified property. Only
> + properties that are listed as readwrite are
> + changeable. On success a PropertyChanged signal
> + will be emitted.
> +
> + Possible Errors: [service].Error.InProgress
> + [service].Error.InvalidArguments
> + [service].Error.Failed
> +
> +Signals PropertyChanged(string property, variant value)
> +
> + This signal indicates a changed value of the given
> + property.
> +
> +Properties string DefaultAPN [readwrite]
To be consistent with ConnectionContext, which spells out APN as
'AccessPointName', we do something like DefaultAccessPointName
> +
> + On LTE, contexts activate automatically. This property
> + allows selection of an APN to be used on next
> + automatic activation.
> +
> + Setting this property to an empty string clears the
> + default APN from the modem.
>
Why do you have the protocol in Patch 1? Do you want to include this here ?
Regards,
-Denis
next prev parent reply other threads:[~2016-11-09 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 17:43 [PATCH 0/9] RFC: add LTE atom Dragos Tatulea
2016-11-09 17:43 ` [PATCH 1/9] include: add header file for lte atom Dragos Tatulea
2016-11-09 20:19 ` Denis Kenzior
2016-11-09 17:43 ` [PATCH 2/9] src: ofono.h: add LTE atom define Dragos Tatulea
2016-11-09 20:20 ` Denis Kenzior
2016-11-09 17:43 ` [PATCH 3/9] lte: add implementation for LTE atom Dragos Tatulea
2016-11-09 20:37 ` Denis Kenzior
2016-11-09 17:43 ` [PATCH 4/9] build: add lte atom support Dragos Tatulea
2016-11-09 17:43 ` [PATCH 5/9] test: add script for setting lte atom properties Dragos Tatulea
2016-11-09 17:43 ` [PATCH 6/9] doc: add lte atom documentation Dragos Tatulea
2016-11-09 20:41 ` Denis Kenzior [this message]
2016-11-09 17:43 ` [PATCH 7/9] ubloxmodem: add lte atom driver Dragos Tatulea
2016-11-09 20:43 ` Denis Kenzior
2016-11-09 17:43 ` [PATCH 8/9] build: add support for ublox " Dragos Tatulea
2016-11-09 17:43 ` [PATCH 9/9] plugins: ublox: enable lte driver for tobyl2 Dragos Tatulea
-- strict thread matches above, loose matches on Subject: below --
2016-11-10 16:55 [PATCH v2 0/9] add LTE atom Dragos Tatulea
2016-11-10 16:55 ` [PATCH 6/9] doc: add lte atom documentation Dragos Tatulea
2016-11-11 16:50 ` 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=582389E0.3070309@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