From: Ashok Raj Nagarajan <arnagara@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Ashok Raj Nagarajan <arnagara@qti.qualcomm.com>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] ath10k: add support for controlling tx power to a station
Date: Wed, 01 Feb 2017 23:14:50 +0530 [thread overview]
Message-ID: <0c8b88d40b3adc0f09ade2780ed1d994@codeaurora.org> (raw)
In-Reply-To: <cbb69298-391d-b3d5-5a84-5792fe170f95@candelatech.com>
On 2017-02-01 00:27, Ben Greear wrote:
> On 01/31/2017 10:42 AM, Ashok Raj Nagarajan wrote:
>> This patch will add the support to control the transmit power for
>> traffic
>> to a station associated with the AP. Userspace provide the transmit
>> power
>> value in mBm units and the allowed range is from 0 to 70. Underlying
>> FW
>
> How did you come up with 70 mBm as the limit. This is only 7dBm?
>
> I would expect it to match the range of normal tx-power which is likely
> up to
> 30 dBm or so on some NICs (not counting regulatory limit).
>
I think I will have to re-word the commit log a bit. ath10k driver would
get the value in dBm only and the range is from 0 to 70 dBm. Looking at
the db.txt, I see a max value of 44 dm for a 60GHz channel. SO to be
little future proof having a greater acceptable range from user. The
final tx power will be calculated based on this extra parameter the user
passes on, including the regulatory limit for the channel.
Thanks,
Ashok
> Thanks,
> Ben
next prev parent reply other threads:[~2017-02-01 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 18:42 [PATCH v2] ath10k: add support for controlling tx power to a station Ashok Raj Nagarajan
2017-01-31 18:57 ` Ben Greear
2017-02-01 17:44 ` Ashok Raj Nagarajan [this message]
2017-02-01 18:05 ` Ben Greear
2017-01-31 21:03 ` kbuild test robot
2017-01-31 21:54 ` kbuild test robot
2017-02-02 7:44 ` Valo, Kalle
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=0c8b88d40b3adc0f09ade2780ed1d994@codeaurora.org \
--to=arnagara@codeaurora.org \
--cc=arnagara@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox