From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail2.candelatech.com ([208.74.158.173]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZbLrI-0001sl-IR for ath10k@lists.infradead.org; Mon, 14 Sep 2015 04:59:17 +0000 Received: from [192.168.3.193] (unknown [50.34.182.146]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail2.candelatech.com (Postfix) with ESMTPSA id 5823340D706 for ; Sun, 13 Sep 2015 21:58:54 -0700 (PDT) Message-ID: <55F6540D.9080300@candelatech.com> Date: Sun, 13 Sep 2015 21:58:53 -0700 From: Ben Greear MIME-Version: 1.0 Subject: Need to re-associate firmware peer when SMPS_CHANGED is set? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: ath10k While digging in 10.1 firmware, I notice that setting WMI_PEER_SMPS_STATE can cause the chainmask to change. And, that in turn can change all sorts of things related to available rates and such. Maybe we should do a re-assoc when we notice SMPS_CHANGED, similar to how it is done for NSS_CHANGED? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k