Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp579016ybz; Wed, 22 Apr 2020 04:06:11 -0700 (PDT) X-Google-Smtp-Source: APiQypIfVAoJbrIFnKmI2xjj/ClFOhjiN229e0bEDhRQQR0AQlwJyvjMzK/JAl6tcZBbUASBQeDW X-Received: by 2002:a17:907:447f:: with SMTP id oo23mr24851204ejb.274.1587553571448; Wed, 22 Apr 2020 04:06:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587553571; cv=none; d=google.com; s=arc-20160816; b=VlCjo69NQdIqWzY/Q56UQ25V4Gy8a/slaWQv7DCKhcgvw+mQ7vAapeOC2lUu2LcKeB 2qpi9uUAdGy89DLaQLWoC+OVQcyUE6snClVzgkKgweHFgfX+AlqPtKubbkju/ZP0MUHP 7mILAtltpaxUt2WTXSNmtQRITwvWkK2zNOrkWpZq8GX1n1YB8HNWNj7FJ183LCz7AMNA lyLJ9wkZjKlJG3brvBsLZjYeKTmjqRvMMHECkCCxaFcPlOD50SvHWUANI1/N/voa0IdZ Y84IAc1UrRb5VijjLoXyhVcpmmIWJKlhr6cB55oBwuxLxgjJiBoyrGN04BCSf8+Qj9la 22YQ== 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=3z5ilxWvc6P1SJ+zfhACnUU9hZ1An/VzTjxF25Njkao=; b=J8svJ2bV9K3GfgVzG3qWGLHBDCk/JOYTxxyDaEDrX+pBokgbwuQtlugxHam4TJkDKM wOopenD3ZEpIbokv4s8eI8Rkks/Huu4cmleL11DYe+zhj9kNeYe6of5EPFVffqmyBV9E 7mLDGtN0+qCJ++TK2R78xEVBNbO/16EgzOkhrRio43nDLkMVQs/3hCJe/3KsXE3kZko/ UeOBnCU/EiQQiQHDUbUztkBYG6yUAPai3qkvKqSX3VVb4APQZD4wHDvBHCbkOky5eL1N r88hizU/3CeXaOs3APWZF9GZLSuVRLrwICH9vuMGjHmv0bI7J7WyA/Hre5xszqP09UlC co1g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d9F5UJPL; 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 e25si3307117ejl.159.2020.04.22.04.05.48; Wed, 22 Apr 2020 04:06:11 -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=d9F5UJPL; 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 S1732471AbgDVLDW (ORCPT + 99 others); Wed, 22 Apr 2020 07:03:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:46946 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726589AbgDVKAA (ORCPT ); Wed, 22 Apr 2020 06:00:00 -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 2B99F2077D; Wed, 22 Apr 2020 09:59:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587549599; bh=x8S4j1AKPDX8Tcy3wit8RvIVRrO7ULq6y5vs+Y272sw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=d9F5UJPLCJNAy6MRjBXXXNGLYsZjp/HCN0+iSvQ5xhUdGGtorAbiMmWl14JGmH298 CY3wkVj7n/BsYImnl9Eg02sm7KTJOI9ymYXhm8HFDdQUk39gozal4fkWgEICd9aTJo MIKs7Uly5lu3uBsLwIv28CE8lMBR+KmMSS4jOhxU= 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.4 030/100] ath9k: Handle txpower changes even when TPC is disabled Date: Wed, 22 Apr 2020 11:56:00 +0200 Message-Id: <20200422095028.270207232@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200422095022.476101261@linuxfoundation.org> References: <20200422095022.476101261@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 @@ -1437,6 +1437,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);