eeepc-laptop: check the 3G rfkill state on resume

All the rfkill devices are treated as "persistent", 3G is no exception.
This means their state may change over hibernation.

Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Signed-off-by: Corentin Chary <corentincj@iksaif.net>
Signed-off-by: Len Brown <len.brown@intel.com>

diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c
index 7f5dfb9..1c929b0 100644 (file)
--- a/drivers/platform/x86/eeepc-laptop.c
+++ b/drivers/platform/x86/eeepc-laptop.c
@@ -845,6 +845,10 @@ static int eeepc_hotk_resume(struct acpi_device *device)
                rfkill_force_state(ehotk->bluetooth_rfkill,
                                   get_acpi(CM_ASL_BLUETOOTH) != 1);
 
+       if (ehotk->wwan3g_rfkill)
+               rfkill_force_state(ehotk->wwan3g_rfkill,
+                                  get_acpi(CM_ASL_3G) != 1);
+
        return 0;
 }