Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp643822ybz; Wed, 22 Apr 2020 05:22:26 -0700 (PDT) X-Google-Smtp-Source: APiQypJI4vaSzbcmpC/UZouTUEq+YaEKQ/vFtk760LVsFoks/n7lIDDta473dl7Iid966SUyYQvR X-Received: by 2002:a17:906:6856:: with SMTP id a22mr22016309ejs.115.1587558146295; Wed, 22 Apr 2020 05:22:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587558146; cv=none; d=google.com; s=arc-20160816; b=WKUngUYF3FdbuXUzTf9A/W+Dq+jYBlEAigdxmiCT4ZDYCjUp3Qzg0LOSzFTFZIeQAa VSJ46prJ/L4a8tHvehLQKGIpECaeahHbyxqSHqijuX7DoG0dKG6joiAG/T+LLYHO2WcM uAvflRuj/ZO0PY/5Py6R4VWmN1iQ/4rogQwjg0aIBsIh9pg3n4n4+FB5pmiBr+S+2Ctw sghI1vWFfsCP054b5ZMgTAC5LSICSWJYNqIKj9s/HTZj/D++kJVlFd5FdRA85f+EmHuA 89r1hwjnDfvqDlGxHUau5m07dJR/M/YED51OQJFEXNoOXqr3nZ01gJCoWP43L1akWl/A QB3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=caruUOfwZWmbXnvABixRUaJOXMhVKmEkAzGZ+Mf3jNg=; b=qhMwTnKp3pPC8r5cLRK8ulJD617dW/pWVLOK5UfmdusrPTGOhBZf9fXMq+MOUSfi/M fco9pONj8xeDjrvxaXFdJ6fVYoHAmFYykaodEjIPj4xB0+JkfzmHKQQ5rNtxJ6R8TeGv /s1RBvmY7NhtqPsN85I9qDvXSxld6PbUg+CqSxTwZvL2TlJKtAOg5l+pM6nwcA9zVjCt bYRRgr9bXOYsexK19hoH860PT3K2l8RZ8k3Da5llJNhAHJ/b04TluCTyA6DDbmi0yuxO CuDa528I0S1gy98w8ptDI73JPNqi/CCl7i3aCfZxHx5bzHoQ9zWNyBKuR0y3ZZmoCFuI oJ1g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=B6MA5Vjo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g24si842143edv.388.2020.04.22.05.22.03; Wed, 22 Apr 2020 05:22:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=B6MA5Vjo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729348AbgDVKMb (ORCPT + 99 others); Wed, 22 Apr 2020 06:12:31 -0400 Received: from mail.kernel.org ([198.145.29.99]:45296 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729324AbgDVKMU (ORCPT ); Wed, 22 Apr 2020 06:12:20 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F33552070B; Wed, 22 Apr 2020 10:12:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587550339; bh=ME0WeMs8A61c6lYVuqvVeOyocXUUkTtNfSPHYXf/LFc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=B6MA5VjoOfIraeP3uJzb6IWjJzGIfcT77CE1Mn2Yde3njpitgCoI7/u9vKTJYsMhq La7L/kOsZboFcapcMqTiT/e7O7HnQ1SVmiWxwoupOnd5UrpDIu2Eik7DwtM7FMhvVe jtHXeUttDnZ+ka0EohJoqhmDbx9ezfaRD9lHuT44= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Remi Pommarel , Kalle Valo Subject: [PATCH 4.14 054/199] ath9k: Handle txpower changes even when TPC is disabled Date: Wed, 22 Apr 2020 11:56:20 +0200 Message-Id: <20200422095103.649955731@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200422095057.806111593@linuxfoundation.org> References: <20200422095057.806111593@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Remi Pommarel commit 968ae2caad0782db5dbbabb560d3cdefd2945d38 upstream. When TPC is disabled IEEE80211_CONF_CHANGE_POWER event can be handled to reconfigure HW's maximum txpower. This fixes 0dBm txpower setting when user attaches to an interface for the first time with the following scenario: ieee80211_do_open() ath9k_add_interface() ath9k_set_txpower() /* Set TX power with not yet initialized sc->hw->conf.power_level */ ieee80211_hw_config() /* Iniatilize sc->hw->conf.power_level and raise IEEE80211_CONF_CHANGE_POWER */ ath9k_config() /* IEEE80211_CONF_CHANGE_POWER is ignored */ This issue can be reproduced with the following: $ modprobe -r ath9k $ modprobe ath9k $ wpa_supplicant -i wlan0 -c /tmp/wpa.conf & $ iw dev /* Here TX power is either 0 or 3 depending on RF chain */ $ killall wpa_supplicant $ iw dev /* TX power goes back to calibrated value and subsequent calls will be fine */ Fixes: 283dd11994cde ("ath9k: add per-vif TX power capability") Cc: stable@vger.kernel.org Signed-off-by: Remi Pommarel Signed-off-by: Kalle Valo Signed-off-by: Greg Kroah-Hartman --- drivers/net/wireless/ath/ath9k/main.c | 3 +++ 1 file changed, 3 insertions(+) --- a/drivers/net/wireless/ath/ath9k/main.c +++ b/drivers/net/wireless/ath/ath9k/main.c @@ -1456,6 +1456,9 @@ static int ath9k_config(struct ieee80211 ath_chanctx_set_channel(sc, ctx, &hw->conf.chandef); } + if (changed & IEEE80211_CONF_CHANGE_POWER) + ath9k_set_txpower(sc, NULL); + mutex_unlock(&sc->mutex); ath9k_ps_restore(sc);