I'm a bit of a kernel n00b here, but it's unclear to me that this is the right thing to do and I just wanted to get some clarity. If the ath11k device fails to suspend, my understanding is that it might waste power attempting to talk to the host that's currently asleep. Are we sure that ath11k can recover from ignored failures/skipped teardown? On Wed, Feb 22, 2023 at 2:34 AM Kalle Valo <kvalo@xxxxxxxxxx> wrote: > > Len Brown <len.brown@xxxxxxxxx> wrote: > > > When ath11k runs into internal errors upon suspend, > > it returns an error code to pci_pm_suspend, which > > aborts the entire system suspend. > > > > The driver should not abort system suspend, but should > > keep its internal errors to itself, and allow the system > > to suspend. Otherwise, a user can suspend a laptop > > by closing the lid and sealing it into a case, assuming > > that is will suspend, rather than heating up and draining > > the battery when in transit. > > > > In practice, the ath11k device seems to have plenty of transient > > errors, and subsequent suspend cycles after this failure > > often succeed. > > > > https://bugzilla.kernel.org/show_bug.cgi?id=216968 > > > > Fixes: d1b0c33850d29 ("ath11k: implement suspend for QCA6390 PCI devices") > > > > Signed-off-by: Len Brown <len.brown@xxxxxxxxx> > > Cc: stable@xxxxxxxxxxxxxxx > > Patch applied to wireless.git, thanks. > > 7c15430822e7 wifi: ath11k: allow system suspend to survive ath11k > > -- > https://patchwork.kernel.org/project/linux-wireless/patch/20230201183201.14431-1-len.brown@xxxxxxxxx/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches >
