fix: update from upstream

See https://github.com/nrfconnect/sdk-nrf/tree/fb26c51ddcc240517984fde76aeadaa00e9337c0/applications/asset_tracker_v2
NordicSemiconductor · Nov 9, 2023 · 8f087dd · 8f087dd
1 parent dcd6ed7
commit 8f087dd
Show file tree

Hide file tree

Showing 6 changed files with 270 additions and 294 deletions.
diff --git a/doc/cloud_module.rst b/doc/cloud_module.rst
@@ -82,7 +82,7 @@ nRF Cloud A-GNSS and P-GPS
 ==========================
 
 When the cloud module is configured to communicate with `AWS IoT Core`_, `Azure IoT Hub`_, or an `LwM2M`_ server, it supports processing of received A-GNSS and P-GPS data using the :ref:`lib_nrf_cloud_agnss` and :ref:`lib_nrf_cloud_pgps` libraries.
-This enables the cloud service to fetch A-GNSS and P-GPS data directly from `nRF Cloud`_ using REST calls and relay this data to an nRF91 Series SiP using the pre-established cloud connection.
+This enables the cloud service to fetch A-GNSS and P-GPS data directly from `nRF Cloud`_ and relay this data to an nRF91 Series SiP using the pre-established cloud connection.
 By reusing the pre-established connection, the application saves overhead related to maintaining multiple connections at the same time.
 When configuring the application to communicate with nRF Cloud, A-GNSS and P-GPS data are received directly from the service, and not by proxy.
 For more information, see `nRF Cloud Location Services <nRF Cloud Location Services documentation_>`_.
@@ -114,7 +114,7 @@ Reconnection is implemented with a binary backoff based on the following lookup
 .. code-block:: c
 
    static struct cloud_backoff_delay_lookup backoff_delay[] = {
-      { 32 }, { 64 }, { 128 }, { 256 }, { 512 },
+      { 32 }, { 64 }, { 128 }, { 256 }, { 512 }, { 1024 },
       { 2048 }, { 4096 }, { 8192 }, { 16384 }, { 32768 },
       { 65536 }, { 131072 }, { 262144 }, { 524288 }, { 1048576 }
    };

diff --git a/doc/data_module.rst b/doc/data_module.rst
@@ -10,9 +10,6 @@ Data module
 The data module gathers data that has been sampled by other modules in the system and stores it into ring buffers.
 It keeps track of data requested by the :ref:`asset_tracker_v2_app_module` and decides when data is sent to the cloud.
 
-.. note::
-   The data module will undergo substantial refactoring soon. Hence, some of its features are not currently documented.
-
 Features
 ********
 

diff --git a/src/events/data_module_event.c b/src/events/data_module_event.c
@@ -28,8 +28,6 @@ static char *get_evt_type_str(enum data_module_event_type type)
 		return "DATA_EVT_IMPACT_DATA_SEND";
 	case DATA_EVT_CLOUD_LOCATION_DATA_SEND:
 		return "DATA_EVT_CLOUD_LOCATION_DATA_SEND";
-	case DATA_EVT_AGNSS_REQUEST_DATA_SEND:
-		return "DATA_EVT_AGNSS_REQUEST_DATA_SEND";
 	case DATA_EVT_CONFIG_INIT:
 		return "DATA_EVT_CONFIG_INIT";
 	case DATA_EVT_CONFIG_READY:

diff --git a/src/events/data_module_event.h b/src/events/data_module_event.h
@@ -77,15 +77,6 @@ enum data_module_event_type {
 	 */
 	DATA_EVT_CLOUD_LOCATION_DATA_SEND,
 
-	/** Send A-GNSS request.
-	 *  The event has an associated payload of type @ref data_module_data_buffers in
-	 *  the `data.buffer` member.
-	 *
-	 *  If a non LwM2M build is used the data is heap allocated and must be freed after use by
-	 *  calling k_free() on `data.buffer.buf`.
-	 */
-	DATA_EVT_AGNSS_REQUEST_DATA_SEND,
-
 	/** Send the initial device configuration.
 	 *  The event has an associated payload of type @ref cloud_data_cfg in
 	 *  the `data.cfg` member.