SNIP_CLASSIC_PWM_SECTION_8_5_1_Pwm_Main_PowerTransitionManager

8.5.1 Pwm_Main_PowerTransitionManager [SWS_Pwm_00189] Definition of scheduled function Pwm_Main_PowerTransitionManager ⌈ Service Name Pwm_Main_PowerTransitionManager Syntax void Pwm_Main_PowerTransitionManager ( void ) Service ID [hex] 0x0d Description This API is cyclically called and supervises the power state transitions, checking for the readiness of the module and issuing the callbacks IoHwAb_Pwm_NotifyReadyForPower State<Mode> (see PwmPowerStateReadyCbkRef configuration parameter). Available via SchM_Pwm.h ⌋ [SWS_Pwm_00190] ⌈This API executes any non-immediate action needed to finalize a power state transition requested by Pwm_PreparePowerState.⌋ [SWS_Pwm_00191] ⌈The rate of scheduling shall be defined by Pwm MainSchedulePeriod and shall be variable, as the function only needs to be called if a transition has been requested.⌋ [SWS_Pwm_00192] ⌈This API shall also issue callback notifications to the eventually registered users (IoHwAbs) as configured, only in case the asynch mode is chosen.⌋ [SWS_Pwm_00193] ⌈In case the PWM module is not initialized, this function shall simply return without any further elaboration. This is needed to avoid to elaborate uninitialized variables. No development error shall be entered, because this condition can easily be verified during the startup phase (tasks started before the initialization is complete). Rationale: during the startup phase it can happen that the OS already schedules tasks, which call main functions, while some modules are not initialised yet. This is no real error condition, although need handling, i.e. returning without execution. Although the transition state monitoring functionality is mandatory, the implementation of this API is optional, meaning that if the HW allows for other ways to deliver notification and watch the transition state the implementation of this function can be skipped.⌋