From: Oleksij Rempel <linux@rempel-privat.de>
To: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Felix Fietkau" <nbd@openwrt.org>,
"Thomas Hühn" <thomas@net.t-labs.tu-berlin.de>,
adrian@freebsd.org
Subject: Re: [RFC 0/3] add TPC capability for AR9002 based chips
Date: Mon, 29 Dec 2014 14:35:18 +0100 [thread overview]
Message-ID: <54A15896.2020008@rempel-privat.de> (raw)
In-Reply-To: <CAA2SeNKxDk+sgpP9be=8MUgVOBHO26=oA4r4v+wRHfN1b6fH8w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
Am 28.12.2014 um 15:32 schrieb Lorenzo Bianconi:
>> Hi, can you please describe some testcases for you patches.
>>
>
> This patchset adds Transmission Power Control (TPC) for AR9002 based
> chips. IOW it enables the capability of correct TX power on per-packet
> basis. It is preparatory for upcoming Thomas's joint rate and power
> control
> algorithm.
Do you mean, right now there is no way to test your patches?
> Regards,
> Lorenzo
>
>> Am 27.12.2014 um 15:12 schrieb Lorenzo Bianconi:
>>> This patchset adds TPC capability to ath9k for AR9002 based chips
>>>
>>> *[RFC 1/3]: add TX power per-rate tables to cap TX power in TX descriptor path
>>> *[RFC 2/3]: cap per-packet TX power according to TX power per-rate tables
>>> *[RFC 3/3]: enable per-packet TPC on AR9002 based chips by default
>>>
>>> This pachset is based on Adrian Chadd's hints
>>> (https://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg10396.html)
>>>
>>> Lorenzo Bianconi (3):
>>> ath9k: add power per-rate tables for AR9002 chips
>>> ath9k: add TPC to TX path for AR9002 based chips
>>> ath9k: enable per-packet TPC on AR9002 based chips
>>>
>>> drivers/net/wireless/ath/ath9k/ar5008_phy.c | 80 ++++++++++++++++++++++++++++
>>> drivers/net/wireless/ath/ath9k/debug.c | 5 --
>>> drivers/net/wireless/ath/ath9k/eeprom_4k.c | 14 +++++
>>> drivers/net/wireless/ath/ath9k/eeprom_9287.c | 15 ++++++
>>> drivers/net/wireless/ath/ath9k/eeprom_def.c | 14 +++++
>>> drivers/net/wireless/ath/ath9k/hw.c | 3 +-
>>> drivers/net/wireless/ath/ath9k/hw.h | 2 +
>>> drivers/net/wireless/ath/ath9k/xmit.c | 66 +++++++++++++++++++----
>>> 8 files changed, 181 insertions(+), 18 deletions(-)
>>>
>>
>>
>> --
>> Regards,
>> Oleksij
>>
>
>
>
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2014-12-29 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 14:12 [RFC 0/3] add TPC capability for AR9002 based chips Lorenzo Bianconi
2014-12-27 14:12 ` [RFC 1/3] ath9k: add power per-rate tables for AR9002 chips Lorenzo Bianconi
2014-12-27 14:12 ` [RFC 2/3] ath9k: add TPC to TX path for AR9002 based chips Lorenzo Bianconi
2014-12-27 14:12 ` [RFC 3/3] ath9k: enable per-packet TPC on " Lorenzo Bianconi
2014-12-28 12:46 ` [RFC 0/3] add TPC capability for " Oleksij Rempel
2014-12-28 14:32 ` Lorenzo Bianconi
2014-12-29 13:35 ` Oleksij Rempel [this message]
2014-12-29 14:18 ` Lorenzo Bianconi
2014-12-30 10:18 ` Oleksij Rempel
2014-12-30 11:00 ` Lorenzo Bianconi
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=54A15896.2020008@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=adrian@freebsd.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=nbd@openwrt.org \
--cc=thomas@net.t-labs.tu-berlin.de \
/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).