On 1/18/2023 10:00 PM, Johannes Berg wrote:
+++ b/include/net/cfg80211.h
@@ -5386,6 +5386,8 @@ struct wiphy {
void (*reg_notifier)(struct wiphy *wiphy,
struct regulatory_request *request);
+ void (*beacon_hint_notifier)(struct wiphy *wiphy);
missing doc
On 1/19/2023 7:56 AM, Wen Gong wrote:
On 12/22/2022 8:42 PM, Youghandhar Chintala wrote:
...
+static void ath10k_mac_beacon_notifier(struct wiphy *wiphy)
+{
+ struct ieee80211_hw *hw = wiphy_to_ieee80211_hw(wiphy);
+ struct ath10k *ar = hw->priv;
+
+ if (ath10k_update_channel_list(ar
On 11/14/2022 6:29 PM, Kalle Valo wrote:
Youghandhar Chintala writes:
In a SoC based solution, it would be useful to know the versions of the
various binary firmware blobs the system is running on. On a QCOM based
SoC, this info can be obtained from socinfo debugfs infrastructure. For
this t
On 11/12/2022 1:53 AM, Bjorn Andersson wrote:
On Fri, Nov 11, 2022 at 05:12:35PM +0530, Youghandhar Chintala wrote:
Can you please change the subject to:
wifi: ath10k: Store WLAN firmware version in SMEM image table
In a SoC based solution, it would be useful to know the versions of the
vari
On 11/1/2022 2:31 PM, Kalle Valo wrote:
(fixing quotation)
"Youghandhar Chintala (Temp)" writes:
On 10/28/2022 12:19 AM, Jeff Johnson wrote:
On 10/26/2022 3:22 AM, Youghandhar Chintala wrote:
+static void ath10k_qmi_add_wlan_ver_smem(struct ath10k *ar, char
*fw_build_id)
On 10/28/2022 12:19 AM, Jeff Johnson wrote:
On 10/26/2022 3:22 AM, Youghandhar Chintala wrote:
In a SoC based solution, it would be useful to know the versions of the
various binary firmware blobs the system is running on. On a QCOM based
SoC, this info can be obtained from socinfo debugfs infr
