Making 10.1.467 based CT firmware do mgt-over-htt
I have been working on making my CT firmware able to do mgt frames over the normal HTT transport instead of over wmi. This should significantly improve APs that are trying to deal with stations going out of range.
A fairly trivial change in the firmware lets ath10k in station mode associate in both OPEN and WPA2 (I did not test further at this time).
But, on the AP side, this same change ends up with probe responses going out with 10 bytes missing from the end of the frame. If I simply do a skb_put(foo, 10) before sending to firmware, then AP mode works (OPEN, against ath9k AP).
But, this skb_put() breaks the station (OS crashed and rebooted).
I can probably find a particular set of logic that puts or does not put the 10 extra bytes accordingly, but I am curious if anyone knows any reason that AP mode frames are different. I did find some code
in firmware that basically subtracts 10 bytes from length:
len -= (sizeof(struct ieee80211_frame) - WAL_DE_ETHR_HDR_LEN))
This happens for all native wifi pkts though. Is there some reason why a probe response (and maybe other mgt frames?) would not be built for native wifi?
use_frags in htt_tx.c will be TRUE in my case, because htt version is 2.2 in my firmware.
My driver patch looks like this currently:
drivers/net/wireless/ath/ath10k/core.h +1 -0
@@ -570,6 +570,7 @@ struct ath10k {DECLARE_BITMAP (fw_features,ATH10K_FW_FEATURE_COUNT );bool p2p; +bool all_pkts_htt;/* target has no separate mgmt tx command? */ struct {enum ath10k_bus bus;
drivers/net/wireless/ath/ath10k/htt_rx.c +9 -0
@@ -1932,6 +1932,15 @@ void ath10k_htt_t2h_msg_handler(struct ath10k *ar, struct sk_buff *skb)case HTT_T2H_MSG_TYPE_VERSION_CONF : { htt->target_version_major = resp->ver_resp.major; htt->target_version_minor = resp->ver_resp.minor; + +if ((htt->target_version_major >=3 ) || +/* CT firmware with HTT-MGT */ + (htt->target_version_major ==2 && + htt->target_version_minor ==2 )) + ar->all_pkts_htt = true; +else + ar->all_pkts_htt = false; +complete (&htt->target_version_received);break ; }
drivers/net/wireless/ath/ath10k/htt_tx.c +5 -1
@@ -459,6 +459,10 @@ int ath10k_htt_tx(struct ath10k_htt *htt, struct sk_buff *msdu) } skb_cb->htt.txbuf_paddr = paddr; +if (ieee80211_is_mgmt (hdr->frame_control)) { +skb_put (msdu,10 ); + } + if ((ieee80211_is_action(hdr->frame_control) || ieee80211_is_deauth(hdr->frame_control) || ieee80211_is_disassoc(hdr->frame_control)) &&
@@ -546,7 +550,7 @@ int ath10k_htt_tx(struct ath10k_htt *htt, struct sk_buff *msdu)"htt tx flags0 %hhu flags1 %hu len %d id %hu frags_paddr %08x, msdu_paddr %08x vdev %hhu tid %hhu freq %hu\n" , flags0, flags1, skb_len, msdu_id, frags_paddr, (u32)skb_cb->paddr, vdev_id, tid, skb_cb->htt.freq); -ath10k_dbg_dump (ar,ATH10K_DBG_HTT_DUMP ,NULL ,"htt tx msdu: " , +ath10k_dbg_dump (ar,ATH10K_DBG_HTT /*_DUMP*/ ,NULL ,"htt tx msdu: " , msdu->data, skb_len);trace_ath10k_tx_hdr (ar, msdu->data, msdu->len);trace_ath10k_tx_payload (ar, msdu->data, msdu->len);
drivers/net/wireless/ath/ath10k/mac.c +1 -1
@@ -2309,7 +2309,7 @@ static void ath10k_tx_htt(struct ath10k *ar, struct sk_buff *skb)struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)skb->data;int ret =0 ; -if (ar->htt.target_version_major >=3 ) { +if (ar->all_pkts_htt) {/* Since HTT 3.0 there is no separate mgmt tx command */ ret =ath10k_htt_tx (&ar->htt, skb); goto exit;
Thanks,
Ben
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 22 lines · Ben Greear
I have been working on making my CT firmware able to do mgt frames over the normal HTT transport instead of over wmi. This should significantly
improve APs that are trying to deal with stations going out of range.A fairly trivial change in the firmware lets ath10k in station mode associate in both
OPEN and WPA2 (I did not test further at this time).But, on the AP side, this same change ends up with probe responses going out with 10 bytes missing from the end of the frame. If I simply do a
skb_put(foo, 10)
before sending to firmware, then AP mode works (OPEN, against ath9k AP).But, this
skb_put()breaks the station (OS crashed and rebooted).I can probably find a particular set of logic that puts or does not put the 10 extra bytes accordingly, but I am curious if anyone knows any reason that AP mode frames are different. I did find some code
in firmware that basically subtracts 10 bytes from length:
len -= (sizeof(struct ieee80211_frame)-WAL_DE_ETHR_HDR_LEN))
Quoted 6 lines
This happens for all native wifi pkts though. Is there some reason why a probe response (and maybe other mgt frames?) would not be built for native wifi?
use_fragsinhtt_tx.cwill be TRUE in my case, because htt version is 2.2 in my firmware.
Perhaps that is the problem right there? HTT 3.0 doesn't use tx frags for mgmt frames. I didn't investigate the reason but I recall someone saying that there are some issues with tx frags for mgmt frames..
Quoted 10 lines
My driver patch looks like this currently:
drivers/net/wireless/ath/ath10k/core.h +0
-0
drivers/net/wireless/ath/ath10k/core.h struct ath10k { · line 573
Quoted 4 lines
drivers/net/wireless/ath/ath10k/core.h +1
-0@@ -570,6 +570,7 @@ struct ath10k {DECLARE_BITMAP (fw_features,ATH10K_FW_FEATURE_COUNT );bool p2p; +bool all_pkts_htt;/* target has no separate mgmt tx command? */
I don't like this idea.
Perhaps we should instead introduce a new IE to explicitly describe what command should be used for mgmt tx? We'd have at least 3 values to express: wmi_mgmt_tx, htt_mgmt_tx, htt_tx.
Quoted 12 lines
drivers/net/wireless/ath/ath10k/core.h +0
-0struct {enum ath10k_bus bus;drivers/net/wireless/ath/ath10k/htt_rx.c +0
-0@@ -1932,6 +1932,15 @@ void ath10k_htt_t2h_msg_handler(struct ath10k *ar, struct sk_buff *skb)case HTT_T2H_MSG_TYPE_VERSION_CONF : { htt->target_version_major = resp->ver_resp.major;
drivers/net/wireless/ath/ath10k/htt_rx.c void ath10k_htt_t2h_msg_handler(struct ath10k *ar, · line 1944
Quoted 10 lines
drivers/net/wireless/ath/ath10k/htt_rx.c +9
-0htt->target_version_minor = resp->ver_resp.minor; + +if ((htt->target_version_major >=3 ) || +/* CT firmware with HTT-MGT */ + (htt->target_version_major ==2 && + htt->target_version_minor ==2 )) + ar->all_pkts_htt = true; +else + ar->all_pkts_htt = false; +
I wouldn't rely on HTT versioning...
Michał
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 27 lines · Michal Kazior
Quoted 26 lines · Ben Greear
I have been working on making my CT firmware able to do mgt frames over the normal HTT transport instead of over wmi. This should significantly
improve APs that are trying to deal with stations going out of range.A fairly trivial change in the firmware lets ath10k in station mode associate in both
OPEN and WPA2 (I did not test further at this time).But, on the AP side, this same change ends up with probe responses going out with 10 bytes missing from the end of the frame. If I simply do a
skb_put(foo, 10)
before sending to firmware, then AP mode works (OPEN, against ath9k AP).But, this
skb_put()breaks the station (OS crashed and rebooted).I can probably find a particular set of logic that puts or does not put the 10 extra bytes accordingly, but I am curious if anyone knows any reason that AP mode frames are different. I did find some code
in firmware that basically subtracts 10 bytes from length:
len -= (sizeof(struct ieee80211_frame)-WAL_DE_ETHR_HDR_LEN))This happens for all native wifi pkts though. Is there some reason why a probe response (and maybe other mgt frames?) would not be built for native wifi?
Quoted 6 lines
Quoted 2 lines
use_fragsinhtt_tx.cwill be TRUE in my case, because htt version is 2.2 in my firmware.Perhaps that is the problem right there? HTT 3.0 doesn't use tx frags for mgmt frames. I didn't investigate the reason but I recall someone saying that there are some issues with tx frags for mgmt frames..
Yeah, but I am not sure what that would be at this point. Possibly this was just laziness on part of firmware or some other hack. If someone does know this reason, I'm interested in learning it.
Quoted 11 lines
Quoted 11 lines
My driver patch looks like this currently:
drivers/net/wireless/ath/ath10k/core.h +0
-0@@ -570,6 +570,7 @@ struct ath10k {DECLARE_BITMAP (fw_features,ATH10K_FW_FEATURE_COUNT );
Quoted 8 lines
drivers/net/wireless/ath/ath10k/core.h struct ath10k { · line 573
Quoted 2 lines
drivers/net/wireless/ath/ath10k/core.h +1
-0bool p2p; +bool all_pkts_htt;/* target has no separate mgmt tx command? */ I don't like this idea.
Perhaps we should instead introduce a new IE to explicitly describe what command should be used for mgmt tx? We'd have at least 3 values to express:
wmi_mgmt_tx,htt_mgmt_tx,htt_tx.
I think it is better to calculate these booleans once instead of doing the work each time in the hot path. I would assume this would be more efficient, and also it keeps the hacks to determine the booleans out of the generic code.
Quoted 15 lines
Quoted 15 lines
drivers/net/wireless/ath/ath10k/core.h +0
-0struct {enum ath10k_bus bus;drivers/net/wireless/ath/ath10k/htt_rx.c +3
-0@@ -1932,6 +1932,15 @@ void ath10k_htt_t2h_msg_handler(struct ath10k *ar, struct sk_buff *skb)case HTT_T2H_MSG_TYPE_VERSION_CONF : { htt->target_version_major = resp->ver_resp.major; htt->target_version_minor = resp->ver_resp.minor; + + if ((htt->target_version_major >= 3) || +/* CT firmware with HTT-MGT */
Quoted 8 lines
drivers/net/wireless/ath/ath10k/htt_rx.c void ath10k_htt_t2h_msg_handler(struct ath10k *ar, struct sk_buff *skb) · line 1943
Quoted 6 lines
drivers/net/wireless/ath/ath10k/htt_rx.c +6
-0+ (htt->target_version_major ==2 && + htt->target_version_minor == 2)) + ar->all_pkts_htt = true; + else + ar->all_pkts_htt = false; +I wouldn't rely on HTT versioning...
The code is already doing similar things. Adding IEs are just as risky for me because CT firmware hacks will not be accepted upstream and IEs tend to collide since I cannot reserve enums.
Either way, I suspect there will not be upstream support for my firmware, but if I can get any related code upstream that makes my patches smaller, then I consider that a gain.
Thanks,
Ben
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k