From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Raj Joshi <rajjoshi@comp.nus.edu.sg>
Cc: Ben Greear <greearb@candelatech.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Setting per-frame tx rate for frames injected in raw tx mode
Date: Tue, 17 May 2016 07:43:41 +0000 [thread overview]
Message-ID: <87mvnp6ser.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+uUJGuMrDoXat3rD2AeHTLZUCUDPHXhHVy==62mGLN01O8Vdw@mail.gmail.com> (Raj Joshi's message of "Tue, 17 May 2016 14:14:43 +0700")
Raj Joshi <rajjoshi@comp.nus.edu.sg> writes:
> But I believe there should be some way of fixing rate settings from
> upper layers of the pipeline. iw lets us do manual bitrate
> configuration [2] for ath10k which works as expected. But this only
> helps in setting of rate per-session. I am still finding answers to
> the following questions:
> 1) What is it that iw does that it manages to get the manual bitrate
> configuration?
> 2) How does it ask the firmware to not do any RA and always honor the
> set rate? Basically how does it override the default RA?
The firmware has separate WMI vdev parameters for setting a fixed rate,
check ath10k_mac_op_set_bitrate_mask() for more info.
> 3) Can we do the same on a per-packet basis?
The firmware currently doesn't support that.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-05-17 7:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 6:11 Setting per-frame tx rate for frames injected in raw tx mode Raj Joshi
2016-05-10 16:28 ` Ben Greear
2016-05-11 6:41 ` Raj Joshi
2016-05-11 16:13 ` Ben Greear
2016-05-15 2:40 ` Raj Joshi
2016-05-15 15:17 ` Ben Greear
2016-05-15 17:15 ` Ben Greear
2016-05-17 7:14 ` Raj Joshi
2016-05-17 7:36 ` Michal Kazior
2016-05-17 7:43 ` Valo, Kalle [this message]
2016-05-17 11:43 ` QCA9984 VHT160 support Sebastian Gottschall
2016-05-17 12:00 ` Michal Kazior
[not found] ` <4e407b2c-29f9-3c74-ea94-4206632441c3@dd-wrt.com>
2016-05-17 12:18 ` Michal Kazior
2016-05-17 12:22 ` Sebastian Gottschall
2016-05-17 12:35 ` Sebastian Gottschall
2016-05-17 13:20 ` Valo, Kalle
2016-09-14 10:37 ` Valo, Kalle
2016-09-14 14:38 ` Sebastian Gottschall
2016-09-14 14:44 ` Valo, Kalle
2016-09-16 7:51 ` [PATCH] " Sebastian Gottschall
2016-09-17 6:21 ` unusual event Sebastian Gottschall
2016-10-10 16:04 ` [PATCH] QCA9984 VHT160 support Valo, Kalle
2016-10-10 16:06 ` Valo, Kalle
2016-10-11 1:30 ` Sebastian Gottschall
2016-10-14 10:06 ` Valo, Kalle
2016-10-14 10:14 ` Valo, Kalle
2016-10-18 8:20 ` Sebastian Gottschall
2016-10-18 9:16 ` Sebastian Gottschall
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=87mvnp6ser.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=rajjoshi@comp.nus.edu.sg \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.