Sleep
Functionality to help when putting the system to an EM2/EM3/EM4 sleep states where the high frequency clock is disabled.
Data Structures |
|
struct | RAIL_TimerSyncConfig_t |
Channel values used to perform timer sync before and after sleep.
|
Enumerations |
|
enum |
RAIL_SleepConfig_t
{
RAIL_SLEEP_CONFIG_TIMERSYNC_DISABLED , RAIL_SLEEP_CONFIG_TIMERSYNC_ENABLED } |
The configuration.
|
Functions |
|
void | RAILCb_ConfigSleepTimerSync ( RAIL_TimerSyncConfig_t *timerSyncConfig) |
Configure RAIL timer synchronization.
|
|
RAIL_Status_t | RAIL_ConfigSleep ( RAIL_Handle_t railHandle, RAIL_SleepConfig_t sleepConfig) |
Initialize RAIL timer synchronization.
|
|
RAIL_Status_t | RAIL_Sleep (uint16_t wakeupProcessTime, bool *deepSleepAllowed) |
Stop the RAIL timer and prepare RAIL for sleep.
|
|
RAIL_Status_t | RAIL_Wake ( RAIL_Time_t elapsedTime) |
Wake RAIL from sleep and restart the RAIL timer.
|
|
RAIL_Status_t | RAIL_InitPowerManager (void) |
Initialize RAIL Power Manager.
|
|
RAIL_Status_t | RAIL_DeinitPowerManager (void) |
Stop the RAIL Power Manager.
|
Detailed Description
Functionality to help when putting the system to an EM2/EM3/EM4 sleep states where the high frequency clock is disabled.
The RAIL library has its own timebase and the ability to schedule operations into the future. When going to any power mode that disables the HF clock used for the radio (EM2/EM3/EM4) it is important that this timebase is synchronized to a running LFCLK and the chip is set to wakeup before the next scheduled event. If RAIL has not been configured to use the power manager, RAIL_Sleep and RAIL_Wake must be called for performing this synchronization. If RAIL has been configured to use the power manager, RAIL_InitPowerManager , it will automatically perform timer synchronization based on the selected RAIL_TimerSyncConfig_t . Calls to RAIL_Sleep and RAIL_Wake are unsupported in such a scenario.
Following example code snippets demonstrate synchronizing the timebase with and without timer synchronization:
Sleep with timer synchronization:
When sleeping with timer synchronization you must first get the required LFCLK up and running and leave it running across sleep so that the high frequency clock that drives the RAIL time base can be synchronized to it. The RAIL_Sleep() API will also setup a wake event on the timer to wake up wakeupTime before the next timer event so that it can run successfully. See the EFR32 sections on Low-Frequency Clocks and RAIL Timer Synchronization for more setup details.
This is useful for scenarios where you want to maintain packet timestamps across sleep or use the scheduled RX/TX APIs while sleeping in between. It does take more time and code to do this synchronization so if your application does not need this it should be avoided.
Example (without Power Manager):
Example (with Power Manager):
RAIL APIs such as, RAIL_StartScheduledTx , RAIL_ScheduleRx , RAIL_SetTimer , RAIL_SetMultiTimer can be used to schedule periodic wakeups to perform a scheduled operation. The call to sl_power_manager_sleep() in the main loop ensures that the device sleeps until the scheduled operation is due. Upon completion, each instantaneous or scheduled RX/TX operation will indicate radio busy to the power manager, to allow the application to service the RAIL event and perform subsequent operations before going to sleep. Thus it is important that the application idle the radio by either calling RAIL_Idle or RAIL_YieldRadio . If the radio transitions to RX after an RX or TX operation then one must always call RAIL_Idle in order transition to a lower sleep state. If the radio transitions to idle after an RX or TX operation then RAIL_YieldRadio should suffice in indicating to the power manager that the radio is no longer busy and the device can sleep.
Following example shows scheduling periodic TX on getting a TX completion event:
- Note
- The above code assumes that RAIL automatic state transitions after TX are idle. Set RAIL_SetTxTransitions to ensure the right state transitions. Radio must be idle for the device to enter EM2 or lower energy mode.
- When using the power manager, usage of RAIL_YieldRadio in single protocol RAIL is similar to its usage in multiprotocol RAIL. See Yielding the radio for more details.
- Back to back scheduled operations do not require an explicit call to RAIL_YieldRadio if the radio transitions to idle.
Sleep without timer synchronization:
When sleeping without timer synchronization you are free to enable only the LFCLK's and wake sources required by the application. RAIL will not attempt to configure any wake events and may miss anything that occurs over sleep.
This is useful for scenarios where your application does not care about packet timestamps or scheduling operations accurately over sleep.
Example (without Power Manager):
Example (with Power Manager):
Enumeration Type Documentation
◆ RAIL_SleepConfig_t
enum RAIL_SleepConfig_t |
Function Documentation
◆ RAIL_ConfigSleep()
RAIL_Status_t RAIL_ConfigSleep | ( | RAIL_Handle_t |
railHandle,
|
RAIL_SleepConfig_t |
sleepConfig
|
||
) |
Initialize RAIL timer synchronization.
- Parameters
-
[in] railHandle
A RAIL instance handle. [in] sleepConfig
A sleep configuration.
- Returns
- Status code indicating success of the function call.
◆ RAIL_DeinitPowerManager()
RAIL_Status_t RAIL_DeinitPowerManager | ( | void |
|
) |
Stop the RAIL Power Manager.
- Returns
- Status code indicating success of the function call.
- Note
- The active RAIL configuration must be idle to disable radio power manager and there should be no outstanding requirements by radio power manager.
◆ RAIL_InitPowerManager()
RAIL_Status_t RAIL_InitPowerManager | ( | void |
|
) |
Initialize RAIL Power Manager.
- Returns
- Status code indicating success of the function call.
- Note
- This function should be called only when the application is built and initialized with Power Manager plugin. RAIL will perform timer synchronization, upon transitioning from EM2 or lower to EM1 or higher energy mode or vice-versa, in the Power Manager EM transition callback. Since EM transition callbacks are not called in a deterministic order, it is suggested to not call any RAIL time dependent APIs in an EM transition callback.
◆ RAIL_Sleep()
RAIL_Status_t RAIL_Sleep | ( | uint16_t |
wakeupProcessTime,
|
bool * |
deepSleepAllowed
|
||
) |
Stop the RAIL timer and prepare RAIL for sleep.
- Parameters
-
[in] wakeupProcessTime
Time in microseconds that the application and hardware need to recover from sleep state. [out] deepSleepAllowed
true - system can go to deep sleep. false - system should not go to deep sleep. Deep sleep should be blocked in this case.
- Returns
- Status code indicating success of the function call.
- Warning
- The active RAIL configuration must be idle to enable sleep.
- Note
- This API must not be called if RAIL Power Manager is initialized.
◆ RAIL_Wake()
RAIL_Status_t RAIL_Wake | ( | RAIL_Time_t |
elapsedTime
|
) |
Wake RAIL from sleep and restart the RAIL timer.
- Parameters
-
[in] elapsedTime
Add the sleep duration to the RAIL timer before restarting the RAIL timer.
- Returns
- Status code indicating success of the function call.
If the timer sync was enabled by RAIL_ConfigSleep , synchronize the RAIL timer using an alternate timer. Otherwise, add elapsedTime to the RAIL timer.
- Note
- This API must not be called if RAIL Power Manager is initialized.
◆ RAILCb_ConfigSleepTimerSync()
void RAILCb_ConfigSleepTimerSync | ( | RAIL_TimerSyncConfig_t * |
timerSyncConfig
|
) |
Configure RAIL timer synchronization.
This function is optional to implement.
- Parameters
-
[in,out] timerSyncConfig
A pointer to the RAIL_TimerSyncConfig_t structure containing the configuration parameters for timer sync.
This function is called during RAIL_ConfigSleep to allow an application to configure the PRS and RTCC channels used for timer sync to values other than their defaults. The default channels are populated in timerSyncConfig and can be overwritten by the application. If this function is not implemented by the application, a default implementation from within the RAIL library will be used that simply maintains the default channel values in timerSyncConfig.
If an unsupported channel is selected by the application, RAIL_ConfigSleep will return RAIL_STATUS_INVALID_PARAMETER .