From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k:Descriptor(or Per packet) based TPC
Date: Tue, 24 Nov 2009 09:29:45 -0800 [thread overview]
Message-ID: <20091124172944.GC3726@tux> (raw)
In-Reply-To: <845455.27243.qm@web34302.mail.mud.yahoo.com>
On Tue, Nov 24, 2009 at 09:00:58AM -0800, Anu Krishnamoorthy wrote:
> Hi,
>
> I had implemented descriptor based TPC(per packet TPC) for ath9k by setting the various TxPower control fields within the Tx Descriptor (set11n_txdesc) for the Tx frames. From my testing, for some reason the Tx power values present in the descriptor are not applied by the hardware(I am using ar5416 based card). In contrast, if "iwconfig txpower" (in spite of the known bug) is used(forced to apply by down/up'ing the interface) the power change is noticed from the sniffer.
> Is any additional setup(transmit queue, txdesc interrupt or hardware setup) needs to be done to force the hardware read and process the tx descriptors? Appreciate if any one could shed more light on it or share their own experience if they had tried to implement this feature.
>
> Thanks,
> Ramkumar.
The tx power setting was just set on the sc struct, we likely need a reset so
that when tx power is changed it actually takes effect. There may be an easier
way but I haven't had time to look at this yet.
Luis
next prev parent reply other threads:[~2009-11-24 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 17:00 [ath9k-devel] ath9k:Descriptor(or Per packet) based TPC Anu Krishnamoorthy
2009-11-24 17:29 ` Luis R. Rodriguez [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 18:04 Anu Krishnamoorthy
2009-11-25 2:33 ` Siva Rama Krishna Rao J. Y.
2009-11-25 14:43 ` Anu Krishnamoorthy
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=20091124172944.GC3726@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 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.