From: Sven Eckelmann <sven@narfation.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: nbd@nbd.name, lorenzo.bianconi@redhat.com,
linux-wireless@vger.kernel.org, ryder.lee@mediatek.com,
royluo@google.com
Subject: Re: [PATCH 1/2] mt76: mt7615: init per-channel target power
Date: Tue, 11 Jun 2019 09:28:43 +0200 [thread overview]
Message-ID: <3556594.76tU91ddA5@bentobox> (raw)
In-Reply-To: <ade300b855949dcbe0a278e363415bd56b2e1299.1560234877.git.lorenzo@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Tuesday, 11 June 2019 08:38:52 CEST Lorenzo Bianconi wrote:
> + switch (n_chains) {
> + case 4:
> + target_power += 6;
> + break;
> + case 3:
> + target_power += 4;
> + break;
> + case 2:
> + target_power += 3;
> + break;
> + default:
> + break;
> + }
Any reason why you use different value for 3 chains than ath9k? Following
values are used in ath9k:
* 1 chain: 0 dB
* 2 chains: 3 dB (max combined gain ~3.010299956639812 dB)
* 3 chains: 5 dB (max combined gain ~4.771212547196624 dB)
* 4 chains: not supported (max combined gain 6.020599913279624 dB)
Here are the definitions from ath9k (values are saved in .5 dB steps)
drivers/net/wireless/ath/ath9k/eeprom.h:#define POWER_CORRECTION_FOR_TWO_CHAIN 6 /* 10*log10(2)*2 */
drivers/net/wireless/ath/ath9k/eeprom.h:#define POWER_CORRECTION_FOR_THREE_CHAIN 10 /* 10*log10(3)*2 */
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-11 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 6:38 [PATCH 0/2] take into account external PA when configuring tx power Lorenzo Bianconi
2019-06-11 6:38 ` [PATCH 1/2] mt76: mt7615: init per-channel target power Lorenzo Bianconi
2019-06-11 7:28 ` Sven Eckelmann [this message]
2019-06-11 7:56 ` Lorenzo Bianconi
2019-06-11 6:38 ` [PATCH 2/2] mt76: mt7615: take into account extPA when configuring tx power Lorenzo Bianconi
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=3556594.76tU91ddA5@bentobox \
--to=sven@narfation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=royluo@google.com \
--cc=ryder.lee@mediatek.com \
/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).