diff options
| author | Kai-Heng Feng | 2019-01-13 12:02:54 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman | 2019-01-15 16:11:50 +0100 |
| commit | ac544a459a95fbded20132cc58bb51663c98114c (patch) | |
| tree | 8a57d7cad45912499f7ff97c914768742673ab41 /net/ipv6/ip6_offload.c | |
| parent | staging: rtl8712u: Remove dummy reset-resume callback (diff) | |
| download | kernel-qcow2-linux-ac544a459a95fbded20132cc58bb51663c98114c.tar.gz kernel-qcow2-linux-ac544a459a95fbded20132cc58bb51663c98114c.tar.xz kernel-qcow2-linux-ac544a459a95fbded20132cc58bb51663c98114c.zip | |
staging: rtl8712u: Fix suspend and resume callbacks
When system resume and the rtl8712u dongle didn't lose its power, it
doesn't work quite right:
[ 146.844241] r8712u 2-3:1.0 wlp0s4f1u3: Unable to resume
...
[ 154.029573] r8712u 2-3:1.0 wlp0s4f1u3: In r8711_wx_set_scan: bDriverStopped=1
The !netif_running() check in PM callbacks aren't correct because
rtl8712u doesn't support runtime suspend, so the when the PM ops get
called, it's system suspend or system resume, hence we want to "stop
everthing" or "resume everything".
The NULL check on pnetdev is also redundant, the only place pnetdev can
become NULL is the disconnect callback, which is mutually exclusive to
PM callbacks.
This can make rtl8712u starts working after system resume.
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/ipv6/ip6_offload.c')
0 files changed, 0 insertions, 0 deletions