ath10k: update comment regarding warm reset

The old comment was a little out of date. HTT Rx
ring is a more relevant problem when stopping
transport layer.

Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>

diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index 21f7dc3fb57eeedbe59bd4fce81d3a0a2f7a0a5b..daa38ce29c5e5a4dd88173fdf68e8445d3dbb849 100644 (file)
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
@@ -1243,11 +1243,10 @@ static void ath10k_pci_hif_stop(struct ath10k *ar)
        ath10k_pci_irq_disable(ar);
        ath10k_pci_flush(ar);
 
-       /* Make the sure the device won't access any structures on the host by
-        * resetting it. The device was fed with PCI CE ringbuffer
-        * configuration during init. If ringbuffers are freed and the device
-        * were to access them this could lead to memory corruption on the
-        * host. */
+       /* Most likely the device has HTT Rx ring configured. The only way to
+        * prevent the device from accessing (and possible corrupting) host
+        * memory is to reset the chip now.
+        */
        ath10k_pci_warm_reset(ar);
 
        ar_pci->started = 0;