mbed-os/features/lorawan/lorastack/mac
Hasnain Virk b07c3e791f Reporting scheduling failures
It is quite possible that the user request for scheduling an uplink is deferred because of backoff or if it was a CONFIRMED message, a retry may take place on a different datarate and different channel.
We didn't have a hook for such deferred scheduling, telling the user whether the async rescheduling worked or not. This commit adds that capability and now we can tell the application if a scheduling failure took place after the original schedule request was accepted.
2018-08-01 16:28:00 +03:00
..
LoRaMac.cpp Reporting scheduling failures 2018-08-01 16:28:00 +03:00
LoRaMac.h Reporting scheduling failures 2018-08-01 16:28:00 +03:00
LoRaMacChannelPlan.cpp Remove useless extraction 2018-05-08 16:24:34 +03:00
LoRaMacChannelPlan.h LoRa: Internal include paths corrected 2018-04-10 14:04:18 +03:00
LoRaMacCommand.cpp Lora: Remove obsolete FEATURE_COMMON_PAL flags 2018-05-15 16:08:30 +03:00
LoRaMacCommand.h Lora: Fix battery_level callback 2018-05-11 09:50:24 +03:00
LoRaMacCrypto.cpp Lora: Fix LoRaMacCrypto asserts 2018-05-03 13:04:03 +03:00
LoRaMacCrypto.h Lora: Change LoRaCrypto to a C++ class 2018-04-20 16:01:49 +03:00