From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wr0-x244.google.com ([2a00:1450:400c:c0c::244]) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1e49gT-0004E1-7v for ath10k@lists.infradead.org; Mon, 16 Oct 2017 18:00:16 +0000 Received: by mail-wr0-x244.google.com with SMTP id l1so3785731wrc.3 for ; Mon, 16 Oct 2017 10:59:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <6cbadf5a-4289-640c-eb46-694a7da8ea44@candelatech.com> References: <20160825132522.30994-1-benjamin@sipsolutions.net> <20160825132522.30994-3-benjamin@sipsolutions.net> <6cbadf5a-4289-640c-eb46-694a7da8ea44@candelatech.com> From: Adrian Chadd Date: Mon, 16 Oct 2017 10:59:47 -0700 Message-ID: Subject: Re: [PATCHv3 2/2] ath10k: Allow setting coverage class List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Ben Greear Cc: Simon Wunderlich , Vasanthakumar Thiagarajan , Benjamin Berg , Sebastian Gottschall , "ath10k@lists.infradead.org" , Michal Kazior , Mathias Kretschmer On 16 October 2017 at 10:57, Ben Greear wrote: > On 08/25/2016 06:25 AM, Benjamin Berg wrote: >> >> Unfortunately ath10k does not generally allow modifying the coverage class >> with the stock firmware and Qualcomm has so far refused to implement this >> feature so that it can be properly supported in ath10k. If we however know >> the registers that need to be modified for proper operation with a higher >> coverage class, then we can do these modifications from the driver. >> >> This patch implements this hack for first generation cards which are based >> on a core that is similar to ath9k. The registers are modified in place >> and >> need to be re-written every time the firmware sets them. To achieve this >> the register status is verified after certain WMI events from the >> firmware. >> >> The coverage class may not be modified temporarily right after the card >> re-initializes the registers. This is for example the case during >> scanning. >> >> Thanks to Sebastian Gottschall for initially >> working on a userspace support for this. This patch wouldn't have been >> possible without this documentation. > > > Hello, > > Do you happen to know the maximum distance that can work with this > patch enabled? The register value maximum seems to be 0x3FFF, but I > am not sure of the units (nor how exactly that applies to distance). It's in MAC clocks still, right? So it depends on how fast the MAC clock timer runs. -adrian _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k