From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Specific tx rates with ath10k
Date: Thu, 12 Mar 2015 11:29:11 -0700 [thread overview]
Message-ID: <5501DAF7.1000800@candelatech.com> (raw)
Ath10k firmware gives ability to set specific fixed rate-control rates
for beacons/mgt, multicast, broadcast, and regular traffic.
The ath10k driver only sets regular traffic currently.
I had previously hacked my firmware to just set all rate types when
ath10k driver requested to set the rate.
But, that is not what my customer needs.
So, I am now planning to add some debugfs entries to allow users to set
beacon/mgt, multicast and broadcast rates individually (I don't have time or interest
right now to try patching things top to bottom to try to get this feature
into mac80211 stack or 'iw').
My question is, for when user just runs a command like this:
./local/sbin/iw dev vap1 set bitrates legacy-2.4 6 ht-mcs-2.4
What is the desired behaviour?
Set all rates (beacons/mgt, bcast, multicast, regular) to the same
fixed speed, or just a certain subset of these traffic types?
I can make my firmware do whatever combination is required, and then
users can over-ride the values by using debugfs.....
As a note, ath10k firmware will NOT send beacons at HT speeds, so
if you fix an HT rate, then firmware will ignore that for the beacons/mgt
ratecontrol type.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-03-12 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 18:29 Ben Greear [this message]
2015-03-13 9:37 ` Specific tx rates with ath10k Mário Lopes
2015-03-13 15:56 ` Ben Greear
2015-03-13 17:08 ` Mário Lopes
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=5501DAF7.1000800@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--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).