Return-path: Received: from mail-wr0-f170.google.com ([209.85.128.170]:33246 "EHLO mail-wr0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750714AbdE0Qjb (ORCPT ); Sat, 27 May 2017 12:39:31 -0400 Received: by mail-wr0-f170.google.com with SMTP id w50so15699364wrc.0 for ; Sat, 27 May 2017 09:39:30 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <21095854-07c7-7586-6a6e-e60c11932b84@candelatech.com> References: <21095854-07c7-7586-6a6e-e60c11932b84@candelatech.com> From: Adrian Chadd Date: Sat, 27 May 2017 09:39:29 -0700 Message-ID: (sfid-20170527_183935_533778_07C00D50) Subject: Re: [PATCH] Per chain RSSI reporting To: Ben Greear Cc: Norik Dzhandzhapanyan , "ath10k@lists.infradead.org" , "linux-wireless@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: 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