From: Matthias May <matthias.may@neratec.com>
To: Ben Greear <greearb@candelatech.com>,
Norik Dzhandzhapanyan <norikd@ethertronics.com>,
Adrian Chadd <adrian@freebsd.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] Per chain RSSI reporting
Date: Tue, 30 May 2017 15:23:05 +0200 [thread overview]
Message-ID: <2bc35b78-97b4-bdd8-d8dd-6ec59fa9dbd0@neratec.com> (raw)
In-Reply-To: <82088c50-f800-9d5c-8ccf-879f4b425e66@candelatech.com>
On 27/05/17 23:49, Ben Greear wrote:
> On 05/27/2017 02:41 PM, Norik Dzhandzhapanyan wrote:
>> Yes ~6dB
>
> If a packet is sent on 1 chain with ath10k firmware (9880 hardware, specifically, but probably
> others as well), it will be around 6db higher on that particular chain
> than if the rate-control sends it on all three chains.
>
> Are you measuring on a single chain, or on all of the chains at once and adding
> the power?
>
> I think we would need more detailed reporting using a good third-party device before
> smoothing and RSSI.
>
> Thanks,
> Ben
>
>>
Also noteworthy is that if you measure in a cabled environment and add the signal from multiple chains with a combiner
you will probably measure the power wrong.
The reason for this is that the cyclic shift diversity doesn't work well in a 2 dimensional environment (cable) compared
to the 3 dimensional environment (air).
BR
Matthias
>>
>> From: Ben Greear
>> Sent: Saturday, May 27, 2:38 PM
>> Subject: Re: [PATCH] Per chain RSSI reporting
>> To: Norik Dzhandzhapanyan, Adrian Chadd
>> Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
>>
>>
>> On 05/27/2017 12:25 PM, Norik Dzhandzhapanyan wrote: > We see this inconsistent/incorrect reporting in our RF chamber.
>> How different are the values, and did you sniff with a third-party device to see if it sees the same spikes in RSSI?
>> Thanks, Ben > > Norik > > On 05/27/2017 09:39 AM, Adrian Chadd wrote: >> On 27 May 2017 at 09:07, Ben Greear wrote:
>> >>> At low encoding rates, especially if it switches to a single-chain encoding, >>> maybe the on-air signal really is
>> stronger? >>> >>> Have you verified in some other manner than the signals reported by ath10k >>> are >>> wrong? >>
>> Hiya, >> >> So yeah, multipath, higher TX rates == weaker TX signal, TPC, etc are >> all interesting to know about at
>> the receiver. it's hard to separate >> that out from the noise sometimes, but in some controlled deployments >> its
>> really obvious. >> >> >> >> -adrian >> >> > > > The contents of this transmission are Ethertronics Inc. Confidential
>> and may contain proprietary or legally privileged
>> information which may not be disclosed, copied or distributed without the express written consent of Ethertronics Inc.
>> The information is intended to be for the use of the individual or entity named on this transmission. If you are not
>> the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information
>> is prohibited. If you have received this transmission in error, please notify us by telephone immediately so that we
>> can arrange for the retrieval of the original documents at no cost to you. Alternatively, notify the sender by
>> replying to this transmission and delete the message without disclosing it. Thank you > -- Ben Greear Candela
>> Technologies Inc http://www.candelatech.com
>>
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-05-30 13:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 22:49 [PATCH] Per chain RSSI reporting Norik Dzhandzhapanyan
2017-05-27 1:12 ` Adrian Chadd
2017-05-27 2:09 ` Norik Dzhandzhapanyan
2017-05-27 8:30 ` Norik Dzhandzhapanyan
2017-05-27 16:07 ` Ben Greear
2017-05-27 16:39 ` Adrian Chadd
2017-05-27 17:56 ` Michael Ney
2017-05-27 19:30 ` Norik Dzhandzhapanyan
2017-05-27 22:10 ` Michael Ney
2017-05-28 1:22 ` Norik Dzhandzhapanyan
2017-05-27 19:31 ` Norik Dzhandzhapanyan
2017-05-27 19:25 ` Norik Dzhandzhapanyan
2017-05-27 21:38 ` Ben Greear
[not found] ` <SN1PR08MB13736CC61B1D00ED2968CF5CB0FD0@SN1PR08MB1373.namprd08.prod.outlook.com>
2017-05-27 21:49 ` Ben Greear
2017-05-30 13:23 ` Matthias May [this message]
2017-05-31 13:05 ` Kalle Valo
2017-05-31 12:53 ` Kalle Valo
2017-05-31 12:52 ` Kalle Valo
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=2bc35b78-97b4-bdd8-d8dd-6ec59fa9dbd0@neratec.com \
--to=matthias.may@neratec.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=norikd@ethertronics.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