All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balaji Pothunoori <bpothuno@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
	Ashok Raj Nagarajan <arnagara@codeaurora.org>
Subject: Re: [PATCH] iw: Add support for controlling tx power for per station
Date: Tue, 29 Jan 2019 17:55:17 +0530	[thread overview]
Message-ID: <6ef960abdd335dbfceeae8965c09c850@codeaurora.org> (raw)
In-Reply-To: <28fbd021a9ffd4065ae76fa26872f3041aa87262.camel@sipsolutions.net>

On 2019-01-25 18:05, Johannes Berg wrote:
> On Thu, 2019-01-17 at 18:59 +0530, Balaji Pothunoori wrote:
>> From: Ashok Raj Nagarajan <arnagara@codeaurora.org>
>> 
>> This patch allows userspace to set transmit power,
>> in mBm units, to a station associated to the AP.
>> 
>> To set a limit tx power of 2000 mBm:
>> iw wlan0 station set <mac-addr> txpwr limit 2000
> 
> I would prefer if this was *dBm*, rather than mBm, and be allowed to
> take float values, i.e. this would become "limit 20".
> 
> johannes

Johannes,

Curiously asking, existing txpower set for vap/phy interface will in mBm 
from user space.
why would you suggesting dBm for per peer txpower set?

Existing designs :
root@OpenWrt:~# iw | grep power
         dev <devname> set txpower <auto|fixed|limit> [<tx power in mBm>]
         phy <phyname> set txpower <auto|fixed|limit> [<tx power in mBm>]

Regards,
Balaji.

  reply	other threads:[~2019-01-29 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 13:29 [PATCH] iw: Add support for controlling tx power for per station Balaji Pothunoori
2019-01-25 12:35 ` Johannes Berg
2019-01-29 12:25   ` Balaji Pothunoori [this message]
2019-01-29 12:26     ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2016-06-14 17:46 Ashok Raj Nagarajan
2016-06-14 17:46 ` Ashok Raj Nagarajan

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=6ef960abdd335dbfceeae8965c09c850@codeaurora.org \
    --to=bpothuno@codeaurora.org \
    --cc=arnagara@codeaurora.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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.