SNIP_CLASSIC_LINIF_SECTION_7_1_5_Goto_sleep

7.1.5 Goto sleep The goto-sleep sequence differs between master and slave nodes. In a master node, when the ComM module requests the no communication mode, the LinSM will request the goto-sleep command to be sent on the LIN bus. In a slave node, the LIN Interface indicates the bus sleep event to LinSM, either caused by reception of a goto-sleep command or by detection of a bus idle condition. If the ComM module has requested the no communication mode before, the bus sleep event is forwarded to ComM. Otherwise if the full communication mode requested by Com M module is active, the bus sleep event is not forwarded to ComM, but the wakeup process is restarted by LinSM after the goto-sleep sequence is completed. In all cases, the entering of the no communication mode is notified to BswM and Com M. The callback will always be made, even if there was a problem. [SWS_LinSM_00035] ⌈The LinSM module may only call LinIf_GotoSleep API in Lin If when the state LINSM_FULL_COM and the sub-state LINSM_RUN_COMMUNICATION is active.⌋ [SWS_LinSM_00046] ⌈When LinSM_GotoSleepConfirmation is called, and the current state/substate is LINSM_FULL_COM/LINSM_GOTOSLEEP, the LinSM shall set the state to LINSM_NO_COM, regardless of the "success" parameter. In any other state, the LinSM_GotoSleepConfirmation shall be ignored.⌋ [SWS_LinSM_00302] ⌈If the LinIf_GotoSleep returns E_OK the LinSM sets the sub-state LINSM_GOTOSLEEP.⌋