From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ed1-x541.google.com ([2a00:1450:4864:20::541]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1fkDLD-0006l6-9j for ath10k@lists.infradead.org; Mon, 30 Jul 2018 18:56:24 +0000 Received: by mail-ed1-x541.google.com with SMTP id h4-v6so4553545edi.6 for ; Mon, 30 Jul 2018 11:56:13 -0700 (PDT) Subject: Re: [PATCH] ath10k: Limit available channels via DT ieee80211-freq-limit References: <20180730153933.3771-1-sven.eckelmann@openmesh.com> <5B5F5EF2.2050100@broadcom.com> From: Arend van Spriel Message-ID: <5B5F5F4A.3000302@broadcom.com> Date: Mon, 30 Jul 2018 20:56:10 +0200 MIME-Version: 1.0 In-Reply-To: <5B5F5EF2.2050100@broadcom.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Sven Eckelmann , ath10k@lists.infradead.org Cc: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , linux-wireless@vger.kernel.org T24gNy8zMC8yMDE4IDg6NTQgUE0sIEFyZW5kIHZhbiBTcHJpZWwgd3JvdGU6Cj4gKyBSYWZhxYIK Pgo+IE9uIDcvMzAvMjAxOCA1OjM5IFBNLCBTdmVuIEVja2VsbWFubiB3cm90ZToKPj4gVHJpLWJh bmQgZGV2aWNlcyAoMXggMi40R0h6ICsgMnggNUdIeikgb2Z0ZW4gaW5jb3Jwb3JhdGUgc3BlY2lh bAo+PiBmaWx0ZXJzIGluCj4+IHRoZSBSWCBhbmQgVFggcGF0aC4gVGhlc2UgZmlsdGVyZWQgY2hh bm5lbCBjYW4gaW4gdGhlb3J5IHN0aWxsIGJlIHVzZWQgYnkKPj4gdGhlIGhhcmR3YXJlIGJ1dCB0 aGUgc2lnbmFsIHN0cmVuZ3RoIGlzIHJlZHVjZWQgc28gbXVjaCB0aGF0IGl0IG1ha2VzIG5vCj4+ IHNlbnNlLgo+Pgo+PiBUaGVyZSBpcyBhbHJlYWR5IGEgRFQgcHJvcGVydHkgdG8gbGltaXQgdGhl IGF2YWlsYWJsZSBjaGFubmVscyBidXQgYXRoMTBrCj4+IGhhcyB0byBtYW51YWxseSBjYWxsIHRo aXMgZnVuY3Rpb25hbGl0eSB0byBsaW1pdCB0aGUgY3VycnJlbnRseSBzZXQgd2lwaHkKPj4gY2hh bm5lbHMgZnVydGhlci4KPgo+IFdvbmRlcmluZyB3aGV0aGVyIHdlIGNhbiBjYWxsIGl0IGluIHdp cGh5X3JlZ2lzdGVyKCkgbGlrZSBiZWxvdy4gTm90Cj4gc3VyZSB3aHkgd2UgZGlkIG5vdCBleHBs b3JlIHRoYXQgd2l0aCB0aGUgaW50cm9kdWN0aW9uIG9mIGl0IGJ5IFJhZmHFgi4KPiBNYXliZSBo ZSByZW1lbWJlcnMuIEkgZGlkIG5vdCBmaW5kIHNvbWV0aGluZyBpbiB0aGF0IGRpcmVjdGlvbiBp bgo+IHBhdGNod29yaywgYnV0IG1heSBoYXZlIG1pc3NlZCBpdC4gSSBrbm93IG10NzYgZHJvcHMg dGhlIGJhbmQgcmVmZXJlbmNlCj4gaWYgaXQgZW5kcyB1cCB3aXRoIGFsbCBjaGFubmVscyBkaXNh YmxlZC4gTWF5YmUgdGhhdCB3YXMgdGhlIHJlYXNvbi4KClNvcnJ5IGZvciBzZW5kaW5nIHRoaXMg dHdpY2UuIE15IHdpZmkgY29ubmVjdGlvbiB3YXMgcXVpcmt5LgoKR3IuIEF2UwoKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmF0aDEwayBtYWlsaW5nIGxp c3QKYXRoMTBrQGxpc3RzLmluZnJhZGVhZC5vcmcKaHR0cDovL2xpc3RzLmluZnJhZGVhZC5vcmcv bWFpbG1hbi9saXN0aW5mby9hdGgxMGsK From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ed1-f66.google.com ([209.85.208.66]:42636 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729542AbeG3Ucd (ORCPT ); Mon, 30 Jul 2018 16:32:33 -0400 Received: by mail-ed1-f66.google.com with SMTP id r4-v6so4554778edp.9 for ; Mon, 30 Jul 2018 11:56:12 -0700 (PDT) Subject: Re: [PATCH] ath10k: Limit available channels via DT ieee80211-freq-limit To: Sven Eckelmann , ath10k@lists.infradead.org References: <20180730153933.3771-1-sven.eckelmann@openmesh.com> <5B5F5EF2.2050100@broadcom.com> Cc: linux-wireless@vger.kernel.org, =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= From: Arend van Spriel Message-ID: <5B5F5F4A.3000302@broadcom.com> (sfid-20180730_205616_112214_435FCEB4) Date: Mon, 30 Jul 2018 20:56:10 +0200 MIME-Version: 1.0 In-Reply-To: <5B5F5EF2.2050100@broadcom.com> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 7/30/2018 8:54 PM, Arend van Spriel wrote: > + Rafał > > On 7/30/2018 5:39 PM, Sven Eckelmann wrote: >> Tri-band devices (1x 2.4GHz + 2x 5GHz) often incorporate special >> filters in >> the RX and TX path. These filtered channel can in theory still be used by >> the hardware but the signal strength is reduced so much that it makes no >> sense. >> >> There is already a DT property to limit the available channels but ath10k >> has to manually call this functionality to limit the currrently set wiphy >> channels further. > > Wondering whether we can call it in wiphy_register() like below. Not > sure why we did not explore that with the introduction of it by Rafał. > Maybe he remembers. I did not find something in that direction in > patchwork, but may have missed it. I know mt76 drops the band reference > if it ends up with all channels disabled. Maybe that was the reason. Sorry for sending this twice. My wifi connection was quirky. Gr. AvS