Return-path: Received: from mail2.candelatech.com ([208.74.158.173]:53266 "EHLO mail2.candelatech.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751420AbbFDWMA (ORCPT ); Thu, 4 Jun 2015 18:12:00 -0400 Message-ID: <5570CD2F.4040604@candelatech.com> (sfid-20150605_001205_729038_A406D770) Date: Thu, 04 Jun 2015 15:11:59 -0700 From: Ben Greear MIME-Version: 1.0 To: Michal Kazior CC: c_mpubbi@qti.qualcomm.com, linux-wireless , "ath10k@lists.infradead.org" Subject: Re: [PATCH] ath10k: new debugfs interface to enable adaptive CCA References: <1431093663-15206-1-git-send-email-c_mpubbi@qti.qualcomm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Is there any way to make this work on a 10.1 firmware, even if that means manually poking registers through debugfs? I have a user of CT firmware that would really like Adaptive CCA to work, so if I can just get some clues as to what needs setting, I can write up an API that works with my 10.1 firmware... Thanks, Ben On 05/10/2015 11:05 PM, Michal Kazior wrote: > On 8 May 2015 at 16:01, wrote: >> From: Manikanta Pubbisetty >> >> For devices working in 2.4 GHz to be ETSI compliant, >> it is required to support adaptive CCA. Some firmwares >> support adaptive CCA and is disabled by default. >> >> The patch is an attempt to add a new debugfs interface to enable >> adaptive cca on supported firmwares. Support for this feature is >> advertised with a new firmware feature flag. > > I guess this should be configured automatically depending on DFS > domain. You can't expect users to configure their devices via debugfs, > can you? This should just work. -- Ben Greear Candela Technologies Inc http://www.candelatech.com