summaryrefslogtreecommitdiff
path: root/Documentation/laptops/thinkpad-acpi.txt
diff options
context:
space:
mode:
authorHenrique de Moraes Holschuh <hmh@hmh.eng.br>2010-02-26 04:22:07 +0300
committerHenrique de Moraes Holschuh <hmh@hmh.eng.br>2010-02-26 04:22:07 +0300
commit08fedfc903c78e380b0baa7b57c52d367794d0a5 (patch)
treeec7631cf63d947f5b6ce7dc98cb52c8e568701f7 /Documentation/laptops/thinkpad-acpi.txt
parent7f0cf712a74fcc3ad21f0bde95bd32c2f2cc3888 (diff)
downloadlinux-08fedfc903c78e380b0baa7b57c52d367794d0a5.tar.xz
thinkpad-acpi: fix bluetooth/wwan resume
Studying the DSDTs of various thinkpads, it looks like bit 3 of the argument to SBDC and SWAN is not "set radio to last state on resume". Rather, it seems to be "if this bit is set, enable radio on resume, otherwise disable it on resume". So, the proper way to prepare the radios for S3 suspend is: disable radio and clear bit 3 on the SBDC/SWAN call to to resume with radio disabled, and enable radio and set bit 3 on the SBDC/SWAN call to resume with the radio enabled. Also, for persistent devices, the rfkill core does not restore state, so we really need to get the firmware to do the right thing. We don't sync the radio state on suspend, instead we trust the BIOS to not do anything weird if we never touched the radio state since boot. Time will tell if that's a wise way of doing things... Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Cc: stable@kernel.org
Diffstat (limited to 'Documentation/laptops/thinkpad-acpi.txt')
0 files changed, 0 insertions, 0 deletions