From patchwork Fri Oct 28 16:15:48 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gianfranco Costamagna X-Patchwork-Id: 79979 Delivered-To: patch@linaro.org Received: by 10.140.97.247 with SMTP id m110csp1261384qge; Fri, 28 Oct 2016 09:22:55 -0700 (PDT) X-Received: by 10.98.32.82 with SMTP id g79mr26227559pfg.142.1477671775112; Fri, 28 Oct 2016 09:22:55 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f16si14286151pga.310.2016.10.28.09.22.54; Fri, 28 Oct 2016 09:22:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@yahoo.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761714AbcJ1QWi (ORCPT + 1 other); Fri, 28 Oct 2016 12:22:38 -0400 Received: from nm31-vm1.bullet.mail.ir2.yahoo.com ([212.82.97.88]:44797 "EHLO nm31-vm1.bullet.mail.ir2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761471AbcJ1QWf (ORCPT ); Fri, 28 Oct 2016 12:22:35 -0400 X-Greylist: delayed 405 seconds by postgrey-1.27 at vger.kernel.org; Fri, 28 Oct 2016 12:22:35 EDT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1477671349; bh=Ak8uB9Ey78hGLkFAzwZx68+mFhp+ySGgMn2qTY1tvfQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=AfHkTatYjhu1N0lQQzcgqX9wirzFQZOYoWBmQyFmSFJP9MelxuTf1MAzokn4u1C/rpbF54l4yTpV1r/b+ZuXo08XMTe/UDJe3HWp7HlNX3Ohx7L0sJN7T2QEGJK0tD+zqeb/XVKvcTtWIyJlwRvprK87Qa/8rCuDiuDmODJrnmKOYbt5sBXQfbS29Cce3HonE4NvmeSsNFZ0WsEqU5IKGkIAbL7gvNiO92GcZQ2UvQ0FRTauiP+qI14DYkN0sjj13n/8zm9x2gHLsxesBQ5HQAXG+6BahqZMxEmz10dN/sEnG9dHDy7+JeQTvLuxljiSvRc+gZui/0x0RyIJE9koYQ== Received: from [212.82.98.49] by nm31.bullet.mail.ir2.yahoo.com with NNFMP; 28 Oct 2016 16:15:49 -0000 Received: from [212.82.98.87] by tm2.bullet.mail.ir2.yahoo.com with NNFMP; 28 Oct 2016 16:15:49 -0000 Received: from [127.0.0.1] by omp1024.mail.ir2.yahoo.com with NNFMP; 28 Oct 2016 16:15:49 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 57382.90496.bm@omp1024.mail.ir2.yahoo.com X-YMail-OSG: XqF8hK0VM1kNew0pIX6l2GCVq4bfLeN0Y8c2Jl2h_GDUSF1.9W6OECstmONwvEY aF__gYeK5QWndeowKz2h.BHa_tiTXAIdYfHAAEWTTPSiALNKATg2.PbmDg8iv_JsmoJj0AXBk.u4 C85F7RxJGP0UlAUi3AI4Dl1gXIISD6ZD40cQFPNP3YqBa3ha5SA_WMlCCtSfK2PIymdvJk20ytz6 fcsCFo0ChDdtnZieGc_kXp90YbpOHOLO2ffeFato_WfuzQQs_7lka07sIkGjf2E6Ov5vHHzVbU3W XTrniepagdlF0KJxQm7BOvOeLsjV8nM8vv6e5OBd6DmcMqfSjOhw91F.A9lPImFxXHObZCR.vk83 v4Ej92j4QmFCuZsqooXd2F2wGtAY4BWLr4jkFFaQRPVf6NVNRc9BfiP5ss7wy3deDFgu6DW0VumC QghsrWJk9iCG0mxoWnNaoQofhFvPqgnbuVuAjFwegH7FsoPx1kDDdwxZjIH6oET29GUsJ7bG4Nsg ywDhO386rLiVi9CBLTWJYEmE9TA32nBRfgu84VXt65lFElQSG.kwC2CkXIlS8Mm8MJAc- Received: from jws700046.mail.ir2.yahoo.com by sendmailws162.mail.ir2.yahoo.com; Fri, 28 Oct 2016 16:15:48 +0000; 1477671348.506 Date: Fri, 28 Oct 2016 16:15:48 +0000 (UTC) From: Gianfranco Costamagna Reply-To: Gianfranco Costamagna To: "brcm80211-dev-list@broadcom.com" , "arend.vanspriel@broadcom.com" , "linux-wireless@vger.kernel.org" Cc: "nsmaldone@tierratelematics.com" , "Marco.Arlone@roj.com" Message-ID: <690669269.1124561.1477671348137@mail.yahoo.com> In-Reply-To: References: Subject: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value MIME-Version: 1.0 Content-Length: 2822 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org (resending from my debian.org mail address, to avoid spam filtering) Hi Broadcom developers and linux wireless list. We found a possible issue in the cfg80211 implementation of the regulatory domain rules: .reg_rules = { /* IEEE 802.11b/g, channels 1..11 */ REG_RULE(2412-10, 2472+10, 40, 6, 20, 0), the referred channel 11 has/should have a frequency of 2462, not 2472 (corresponding to channel 13). Is this a typo in the code or the above comment? (I'm not sure why the override of reg.c is in place for 2.4 Ghz frequencies) Can you please double check and in case apply the attached patch? thanks, -- Gianfranco Costamagna >From dc2eaeba8cf3d992a18745cfef1b74bbfc11715b Mon Sep 17 00:00:00 2001 From: Arlone Marco Date: Sat, 22 Oct 2016 15:08:35 +0200 Subject: [PATCH] broadcom cfg80211: fix regulatory channel frequency channel 11 is actually 2462, not 2472 (that is channel 13 instead) Signed-off-by: Gianfranco Costamagna Signed-off-by: Arlone Marco Signed-off-by: Nicola Smaldone --- drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c index b777e1b..d71f959 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c @@ -204,7 +204,7 @@ static const struct ieee80211_regdomain brcmf_regdom = { .alpha2 = "99", .reg_rules = { /* IEEE 802.11b/g, channels 1..11 */ - REG_RULE(2412-10, 2472+10, 40, 6, 20, 0), + REG_RULE(2412-10, 2462+10, 40, 6, 20, 0), /* If any */ /* IEEE 802.11 channel 14 - Only JP enables * this and for 802.11b only -- 2.7.4