From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org
Cc: Bob Copeland <me@bobcopeland.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH v2 3/3] ath11k: register HE mesh capabilities
Date: Wed, 12 Jun 2019 10:42:49 +0200 [thread overview]
Message-ID: <1614431.vQLKkJHT2m@bentobox> (raw)
In-Reply-To: <1919330.hVZVHELXip@bentobox>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Tuesday, 11 June 2019 21:52:20 CEST Sven Eckelmann wrote:
[...]
> if (!test_sta_flag(sta, WLAN_STA_RATE_CONTROL))
> rate_control_rate_init(sta);
>
> /* inform drivers about changes */
> rate_control_rate_update(local, sband, sta, changed);
>
> Both will at least cause a call to ath11k_peer_assoc_prepare +
> ath11k_wmi_send_peer_assoc_cmd but unfortunately the ath11k firmware hangs
> afterwards.
The fw hang seems to be related to the not set bss_conf.he_support in
ath11k_mac_vdev_start_restart. This has to be set when ieee80211_join_mesh
calls ieee80211_vif_use_channel. Otherwise the firmware will set a HT/VHT mode
in the firmware. Any sta with an higher phy mode will just hang the firmware.
So the two main problems right now are:
* set bss_conf.he_support during mesh_join before
ath11k_mac_vdev_start_restart is called
- no clue what the best approach is
* let ath11k redo the association procedure with he_cap->has_he set to true
when wpa_supplicant is in control of the peers.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-12 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:02 [RFC PATCH v2 0/3] mac80211/ath11k: HE mesh support Sven Eckelmann
2019-06-11 18:02 ` [RFC PATCH v2 1/3] mac80211_hwsim: Register support for HE meshpoint Sven Eckelmann
2019-06-11 18:02 ` [RFC PATCH v2 2/3] mac80211: implement HE support for mesh Sven Eckelmann
2019-06-11 18:02 ` [RFC PATCH v2 3/3] ath11k: register HE mesh capabilities Sven Eckelmann
2019-06-11 19:52 ` Sven Eckelmann
2019-06-12 8:42 ` Sven Eckelmann [this message]
2019-06-12 16:34 ` Bob Copeland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1614431.vQLKkJHT2m@bentobox \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).