SNIP_CLASSIC_LIN_SECTION_7_5_1_Background_Rationale

7.5.1 Background & Rationale Following is applicable for LIN master nodes only: The LIN Master node can be awakened either by a wake-up signal generated by one of the slaves, or by a request from the higher layer (LIN interface) (see [SWS_Lin_00209]). The LIN interface controls the message schedule table and so must be able to instruct the LIN driver to put the hardware unit to sleep, or to wake it up (see [SWS_LinIf_00296], [SWS_LinIf_00488]). For this purpose, the LIN driver provides functions to put the LIN channel into its LIN_CH_SLEEP state (see Lin_GoToSleep / Lin_GoToSleepInternal). Following is applicable for LIN slave nodes only: The LIN slave can be awakened either by a wake-up signal generated by the master node or any other slave node on the same channel, or by a request from the higher layer (LIN interface) (see [SWS_Lin_00209]). The LIN Interface detects the conditions to enter sleep mode and instructs the LIN driver to put the hardware unit to sleep, or to wake it up (see [SWS_LinIf_00296], [SWS_LinIf_00488]). For this purpose, the LIN driver provides a function to put the LIN channel into its LIN_CH_SLEEP state (see Lin_GoToSleep / Lin_GoToSleepInternal). Because the slave node cannot transmit a go-to-sleep-command, the function Lin_GoToSleep is not applicable for slave nodes. Following is applicable for LIN master and LIN slave nodes: Upon sleep or wake-up the master must communicate the status change with the rest of the network.