Lines Matching refs:to
16 …CU low-power state, peripheral, memory or clock. Each of these states can be specific to a device.
18 …he management of low-power states in the application and speed up the time-to-market. The SDK Powe…
44 …- The user can specify the low-power state to enter and the resource constraints. If the resource …
45 …- The user is only required to specify the low-power state to enter. All the possible resources sa…
46 … The user is only required to specify the resource constraints. The SDK Power Manager will find th…
55 Firstly the “core” part, is generic across devices and provides APIs to be called in the applicatio…
60 …ates. This part is not intended to be modified by the user. Instead, the application defines the …
68 … and developed by NXP, exposing the pre-defined constraints and easy-to-use APIs to the user for a…
69 Here are examples of APIs to call in the application to leverage the SDK power manager:
70 - **PM_CreateHandle** --> MANDATORY ; Initializes the power manager handler, to be called before us…
72 …cted group. The callback of the group will be called just before the entry to low-power state and …
76 - **PM_RegisterTimerController** --> OPTIONAL ; Register a timer as a wakeup source, to be called w…
78 - **PM_SetConstraints** --> MANDATORY ; Set constraints to Power Manager defined by the user, and/o…
88 …lows the Power Manager to notify created notification groups of power transitions, i.e entry/exit …
90 - **FSL_PM_SUPPORT_WAKEUP_SOURCE_MANAGER** --> Allows the Power Manager to fully manage (create, di…
92 - **FSL_PM_SUPPORT_LP_TIMER_CONTROLLER** --> Allows the Power Manager to control timers.
94 - **FSL_PM_SUPPORT_ALAWAYS_ON_SECTION** --> Allows to store variables in an always-on RAM.
96 For more details on APIs available and description, please refer to the *fsl_pm_core* files.
108 The first step defines the resources the user wants to keep ON/retain for a given low-power state. …
152 `/* Configure the Input Mux block and connect the trigger source to PinInt channel. */`
157 `INPUTMUX_Deinit(INPUTMUX); /* Turnoff clock to inputmux to save power. Clock is only needed to mak…
188 …e is rarely used, as resources are often always requiring as RAM retention to properly wakeup the …
221 …to find the deepest state reachable, it will compare the exit latency of the low power state *exit…
228 …or the sleep state, sleep state will be reached. The resources constraints to keep will be the sum…
235 …esources constraints are also unregistered, thus the resources constraints to keep are *APP_SLEEP_…
239 … should call the *PM_ReleaseConstraints* function as many time as required to fully remove the con…
257 *Parameter:* handle : Pointer to the pm_handle_t structure, upper layer software should pre-allocat…
264 *Parameter:* enable : Used to enable/disable power manager functions.
277 …bution. b. resConstraintsMask logical AND state's lossFeature should equal to 0, because constrain…
284 Register timer controller related functions to power manager.
285 If low power timer is the wakeup source, please remember to register it into power manager by using…
288 handle : Pointer to the pm_handle_t structure.
302 Register critical region related functions to power manager.
304 *Note:* There are multiple-methods to implement critical region(E.g. interrupt controller, locker, …
307 handle : Pointer to the pm_handle_t structure.
308 criticalEntry : Enter critical function to register.
309 criticalExit : Exit critical function to register.
318 notifyElement : The pointer to pm_notify_element_t.
328 notifyElement : The pointer to the notify element to update.
329 callback : The callback function to be updated.
330 data : Pointer to the callback function private data.
337 *Parameter:* notifyElement : The pointer to the notify element to remove.
345 ws : Pointer to the pm_wakeup_source_t variable.
346 wsId : Used to select the wakeup source, the wsId of each wakeup source can be found in fsl_pm_devi…
347 service : The function to be invoked when wake up source asserted.
348 enable : Used to enable/disable the selected wakeup source.
355 *Parameter:* ws : Pointer to the wakeup source object to be enabled.
364 *Parameter:* ws : Pointer to the wakeup source object to be disabled.
371 …it will call the wake-up source callback if it has been registered. Likely to be called from Wake-…
378 If the specific wakeup event occurs, invoke this API to execute its service function.
380 *Parameter:* ws : Pointer to the wakeup source object.
387 Used to set constraints(including power mode constraint and resource constraints)
392 rescNum : The number of resource constraints to be set.
399 Used to release constraints(including power mode constraint and resource constraints)
404 rescNum : The number of resource constraints to be released.
428 …to reduce power consumption in low power states by managing all the resources seemlessly for the u…