summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorSlark Xiao <slark_xiao@163.com>2021-11-08 14:06:48 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-12-08 08:44:07 +0100
commit7e314b4e4b15f7de410cc4ab907a2c55598d14ed (patch)
tree71030d0f12e1e3ad9e3a30060bf4c186dcda0369 /scripts
parenta87097026125a75f2be2116f9f5cdc150c14af62 (diff)
platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep
[ Upstream commit 39f53292181081d35174a581a98441de5da22bc9 ] When WWAN device wake from S3 deep, under thinkpad platform, WWAN would be disabled. This disable status could be checked by command 'nmcli r wwan' or 'rfkill list'. Issue analysis as below: When host resume from S3 deep, thinkpad_acpi driver would call hotkey_resume() function. Finnaly, it will use wan_get_status to check the current status of WWAN device. During this resume progress, wan_get_status would always return off even WWAN boot up completely. In patch V2, Hans said 'sw_state should be unchanged after a suspend/resume. It's better to drop the tpacpi_rfk_update_swstate call all together from the resume path'. And it's confimed by Lenovo that GWAN is no longer available from WHL generation because the design does not match with current pin control. Signed-off-by: Slark Xiao <slark_xiao@163.com> Link: https://lore.kernel.org/r/20211108060648.8212-1-slark_xiao@163.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions