Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:50034 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751874AbeB0EAP (ORCPT ); Mon, 26 Feb 2018 23:00:15 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Date: Tue, 27 Feb 2018 09:30:14 +0530 From: periyasa@codeaurora.org To: Adrian Chadd Cc: Ben Greear , linux-wireless@vger.kernel.org, ath10k@lists.infradead.org, adrian.chadd@gmail.com Subject: Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed" In-Reply-To: References: <1519625792-12010-1-git-send-email-periyasa@codeaurora.org> Message-ID: <83292eb1f9fe6bd2ee9ef82e80693388@codeaurora.org> (sfid-20180227_050019_254318_1225B00C) Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, This is not a bug, Firmware treats every WMI_PEER_ASSOC_CMDID as a new peer assoc. so driver should not give WMI_PEER_ASSOC_CMDID for the already associated peer. For the NSS update, wmi_peer_set_param is enough to update the new NSS value. Regards, Karthikeyan P. On 2018-02-27 00:51, Adrian Chadd wrote: > hi, > > so it's going to eventually leak? Can we fix the firmware bug too? :) > > > -a > > > On 26 February 2018 at 09:06, wrote: >> Hi, >> >> >>> Can you share exactly which resource the firmware ran out of? It >>> would >>> seem to >>> be a FW bug if it is leaking, so maybe it can be fixed as well... >>> >> >> Firmware have total user_id = 528 (512 clients + 16 VAPs). Each >> user_id is >> allocated to peer when Firmware receive the WMI_PEER_ASSOC_CMDID >> request >> from host driver. Firmware free the user_id in peer delete operation. >> >> Regards, >> Karthikeyan P. >> >> _______________________________________________ >> ath10k mailing list >> ath10k@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/ath10k