linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org, nbd@openwrt.org
Subject: Re: [PATCH 1/2] mac80211: Add support of transmit power control (TPC) per data packet
Date: Mon, 30 Jul 2012 09:34:34 +0200	[thread overview]
Message-ID: <1343633674.4452.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1343404809-70329-2-git-send-email-thomas@net.t-labs.tu-berlin.de> (sfid-20120727_180037_367100_88493A5C)

On Fri, 2012-07-27 at 18:00 +0200, Thomas Huehn wrote:

>   * &struct ieee80211_tx_info contains an array of these structs
> - * in the control information, and it will be filled by the rate
> - * control algorithm according to what should be sent. For example,
> - * if this array contains, in the format { <idx>, <count> } the
> + * in the control information, and it will be filled by the joint rate-
> + * power control algorithm according to what should be sent. For example,
> + * if this array contains, in the format { <idx>, <count>, <tpc> } the
>   * information
> - *    { 3, 2 }, { 2, 2 }, { 1, 4 }, { -1, 0 }, { -1, 0 }
> + *    { 3, 2, 16 }, { 2, 2, 10 }, { 1, 4, 5 }, { -1, 0, 0 }
>   * then this means that the frame should be transmitted
> - * up to twice at rate 3, up to twice at rate 2, and up to four
> - * times at rate 1 if it doesn't get acknowledged. Say it gets
> - * acknowledged by the peer after the fifth attempt, the status
> + * up to twice at rate 3 with 16 dBm, up to twice at rate 2 with 10 dBm,

You might want to consider using 1/2 or 1/4 dBm granularity? A lot of
hardware can do that.

>  struct ieee80211_tx_rate {
>  	s8 idx;
>  	u8 count;
>  	u8 flags;
> +	u8 tpc;

I'm not sure that should be named "tpc". Think about what that means --
"transmit power control", but it's really the power value, so it should
be "txpower" or so.

johannes


  reply	other threads:[~2012-07-30  7:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 16:00 [PATCH 0/2] mac80211: Add transmit power control (TPC) support Thomas Huehn
2012-07-27 16:00 ` [PATCH 1/2] mac80211: Add support of transmit power control (TPC) per data packet Thomas Huehn
2012-07-30  7:34   ` Johannes Berg [this message]
2012-07-30 11:29     ` Thomas Huehn
2012-07-30 13:38       ` Johannes Berg
2012-07-27 16:00 ` [PATCH 2/2] mac80211: Add transmit power control support (TPC) for ACK packets Thomas Huehn
2012-07-27 21:36   ` Christian Lamparter
2012-07-28 14:36     ` Thomas Huehn
2012-07-30  7:36   ` Johannes Berg

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=1343633674.4452.3.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).