ff22903a81
There are some cases in which the loading of the Wi-Fi modules may be problematic due to timing conditions: - when a suspend operation in progress is aborted - when Bluetooth is disabled The Wi-Fi needs some time for the system to be ready before loading the modules. This commit: - Stops the Bluetooth before bringing down the Wi-Fi on suspend - Starts the Bluetooth (or adds a small delay) before bringing up the Wi-Fi on resume - Reworks the way the resume operations are programmed, to do them in reverse order (first load the Wi-Fi modules, then bring the interfaces up (if required). It does so by appending/prepending actions into a variable and dumping the contents finally to a temp file. Signed-off-by: Hector Palacios <hector.palacios@digi.com> |
||
|---|---|---|
| .. | ||
| ccimx93 | ||
| 0001-hwclock-add-get-set-parameters-option.patch | ||
| acpid.map | ||
| bridgeifupdown | ||
| busybox-acpid | ||
| busybox-httpd.service.in | ||
| busybox-ntpd | ||
| defconfig | ||
| nm | ||
| poweroff_safe | ||
| pswitch-poweroff | ||
| pswitch-standby | ||
| reboot_safe | ||
| standby | ||
| standby-actions | ||
| standby-systemd | ||