On 02/01/2017 09:44 AM, Ashok Raj Nagarajan wrote:
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.
Why not just accept any value that fits within the storage (u16, probably). The regulatory logic
and other constraints can already make sure that the tx-power is not out-of-bounds, so the user cannot
really break something by attempting to set a large value.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
