michael/zephyr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lorawan: make NVM header documentation backend-agnostic

Browse Source 
Remove loramac-node specific references (LORAMAC_NVM_NOTIFY_FLAG_*)
from the NVM interface documentation, making it suitable for any
LoRaWAN backend implementation.

Signed-off-by: Carlo Caione <ccaione@baylibre.com>
This commit is contained in:
Carlo Caione
2026-01-08 09:19:31 +01:00
committed by Fabio Baltieri
parent 429d98f80d
commit 0a45c8dc70
1 changed files with 5 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
subsys/lorawan/nvm/lorawan_nvm.h
View File

@@ -10,21 +10,13 @@
#include <stdint.h>
/**
* @brief Hook function called when an interrupt related to NVM
* is received from the LoRaWAN stack.
* @brief Hook function called when an NVM update event is received from
* the LoRaWAN stack.
*
* @note This function should not be called directly by the application
* @note This function should not be called directly by the application.
*
* @param flags OR'ed flags received with the interrupt
*
* @see LORAMAC_NVM_NOTIFY_FLAG_NONE
* @see LORAMAC_NVM_NOTIFY_FLAG_CRYPTO
* @see LORAMAC_NVM_NOTIFY_FLAG_MAC_GROUP1
* @see LORAMAC_NVM_NOTIFY_FLAG_MAC_GROUP2
* @see LORAMAC_NVM_NOTIFY_FLAG_SECURE_ELEMENT
* @see LORAMAC_NVM_NOTIFY_FLAG_REGION_GROUP1
* @see LORAMAC_NVM_NOTIFY_FLAG_REGION_GROUP2
* @see LORAMAC_NVM_NOTIFY_FLAG_CLASS_B
* @param flags OR'ed flags indicating which data sections need to be stored.
* The flag values are backend-specific.
*/
void lorawan_nvm_data_mgmt_event(uint16_t flags);