ath/ath10k/mac.c

971 	if (!arvif->beacon)
975 		dma_unmap_single(ar->dev, ATH10K_SKB_CB(arvif->beacon)->paddr,
976 				 arvif->beacon->len, DMA_TO_DEVICE);
982 	dev_kfree_skb_any(arvif->beacon);
984 	arvif->beacon = NULL;
1572 					 mgmt->u.beacon.variable,
1573 					 bcn->len - (mgmt->u.beacon.variable -
1636 		ath10k_warn(ar, "failed to get beacon template from mac80211\n");
1648 	 * so remove it from the base beacon template to avoid duplicate P2P
1649 	 * IEs in beacon frames.
1653 					     u.beacon.variable));
1660 		ath10k_warn(ar, "failed to submit beacon template command: %d\n",
1682 	 /* For mesh, probe response and beacon share the same template */
1711 	 * information is missing, notably SSID. Firmware revisions with beacon
1721 	 * since only wmi-tlv firmware are known to have beacon offload and
1744 	/* Vdev down reset beacon & presp templates. Reinstall them. Otherwise
1750 		ath10k_warn(ar, "failed to update beacon template: %d\n", ret);
2105 	/* Firmware doesn't report beacon loss events repeatedly. If AP probe
2108 	 * which can be cancelled when beacon is received.
2453 		 * beacon interval. Currently we don't know
5630 	/* Some firmware revisions don't wait for beacon tx completion before
5632 	 * (freed) beacon data in some cases, e.g. tx credit starvation
5636 	 * because hw could beacon some random data on the air.  On
5640 	 * Since there are no beacon tx completions (implicit nor explicit)
5643 	 * beacon tx commands. Worst case for this approach is some beacons may
5670 			ath10k_warn(ar, "failed to allocate beacon buffer: %d\n",
6107 			ath10k_warn(ar, "failed to set beacon interval for vdev %d: %i\n",
6113 			   "vdev %d set beacon tx mode to staggered\n",
6120 			ath10k_warn(ar, "failed to set beacon mode for vdev %d: %i\n",
6125 			ath10k_warn(ar, "failed to update beacon template: %d\n",