diff options
author | Aleksander Morgado <aleksander@lanedo.com> | 2012-09-10 13:45:23 +0200 |
---|---|---|
committer | Aleksander Morgado <aleksander@lanedo.com> | 2012-09-14 07:05:22 +0200 |
commit | 4f9817741ff6284c895a90ff15cab3ab056ac21b (patch) | |
tree | cbe6f5b12768b252ed640403ccbc154a9f4ca11c /cli/mmcli.c | |
parent | 83dc9e3e1d32eb72ed60163a066c20d553f4c468 (diff) |
broadband-modem: new methods to lock/unlock current SMS storages
The default AT commands to play with SMS rely on AT+CPMS to select the default
memory storages for different operations. AT+CPMS defines 3 different storages,
called 'mem1' (for reading/listing/deleting), 'mem2' (for storing or sending
from storage) and 'mem3' (for receiving).
For example, when an SMS is to be deleted, we first need to select with AT+CPMS
the proper 'mem1' storage before issuing the command to delete the SMS part.
But, in order to do this properly we need to synchronize the access to the
currently set storages, so that no more than one action is run in the storages
at the same time (e.g. don't store an SMS while another SMS is being deleted).
In order to synchronize this access, we now provide commands to lock()/unlock()
the storages, which should be used when we want to do some operation on them.
Note that this logic is only required because we cannot specify the storage
explicitly in the specific AT command operations. With QMI we don't need this
locking/unlocking.
Diffstat (limited to 'cli/mmcli.c')
0 files changed, 0 insertions, 0 deletions