From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Question rate-mask and iw
Date: Tue, 8 Sep 2015 11:05:49 -0700 [thread overview]
Message-ID: <55EF237D.9070608@candelatech.com> (raw)
I'm trying to add ability to ath10k to set an arbitrary tx-rate mask.
(ie, enable rates 6 64 vht 3 4 9, etc)
I know firmware will need to be modified...that is not the issue currently.
My problem is that I seem not be mis-understanding how the code to set
rates work.
I have this code:
static void ath10k_peer_assoc_h_rate_overrides(struct ath10k *ar,
struct ieee80211_vif *vif,
struct ieee80211_sta *sta,
struct wmi_peer_assoc_complete_arg *arg)
{
struct ath10k_vif *arvif = ath10k_vif_to_arvif(vif);
const struct ieee80211_supported_band *sband;
const struct ieee80211_rate *rates;
u32 ratemask;
int i, j;
int band = ar->hw->conf.chandef.chan->band;
if (! test_bit(ATH10K_FW_FEATURE_WMI_10X_CT, ar->fw_features))
return;
lockdep_assert_held(&ar->conf_mutex);
sband = ar->hw->wiphy->bands[band];
ratemask = sta->supp_rates[band];
rates = sband->bitrates;
ath10k_warn(ar, "band: %d ratemask: 0x%x\n", band, ratemask);
It is called when I run the command below:
iw wlan0 set bitrates legacy-5 6 12
But, rate-mask has all bits set...I would expect only bits corresponding
to rate 6 and 12 to be set.
[ 7487.627841] ath10k_pci 0000:05:00.0: band: 1 ratemask: 0xff
I'll go dig through the stack next..but if anyone has pointers, they would be welcome.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-09-08 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 18:05 Ben Greear [this message]
2015-09-08 18:23 ` Question rate-mask and iw Ben Greear
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=55EF237D.9070608@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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).