linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
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>
Subject: Re: [PATCHv4] mac80211: enable TPC through mac80211 stack
Date: Thu, 08 Jan 2015 08:48:08 +0100	[thread overview]
Message-ID: <1420703288.2029.4.camel@sipsolutions.net> (raw)
In-Reply-To: <CAA2SeN+KZqXcBpOuW=J_vyznOn03NceuH8RDdmcB30-7-9xyQw@mail.gmail.com> (sfid-20150107_153952_445561_A5BF7DBF)

On Wed, 2015-01-07 at 15:39 +0100, Lorenzo Bianconi wrote:

> > Does it really make sense to ask the driver to do "automatic"? After
> > all, there are other limits in mac80211 (like 11h from the AP and
> > regulatory) that need to be considered. So perhaps if userspace says
> > "automatic", the driver should still see only "limited"?
> >
> 
> IMHO "automatic" means lower driver has to take into account just
> channel/regulatory constraints (that is ath9k behavior), since the
> user/mac80211 does not cap TX power, whereas "limited" means the
> user/mac80211 has set a limit for emitted power, so that configuration
> has to be taken into account. 

Well, mac80211 always gives you a max TX power value though - and if
it's only the maximum regulatory permitted on that channel. So there's
always a valid upper bound - unlike the userspace API where "automatic"
means that you have no idea of an upper bound. Inside the kernel you
always have an upper bound, so "automatic" doesn't make that much sense?

johannes


  reply	other threads:[~2015-01-08  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:41 [PATCHv4] mac80211: enable TPC through mac80211 stack Lorenzo Bianconi
2015-01-07 14:12 ` Johannes Berg
2015-01-07 14:39   ` Lorenzo Bianconi
2015-01-08  7:48     ` Johannes Berg [this message]
2015-01-08 11:07       ` Lorenzo Bianconi
2015-01-14  8:29         ` 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=1420703288.2029.4.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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).