From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kalle Valo Subject: Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties Date: Wed, 04 Jan 2017 16:32:44 +0200 Message-ID: <874m1ej3oz.fsf@kamboji.qca.qualcomm.com> References: <20161228155955.25518-1-zajec5@gmail.com> <20170103195514.vf4psb6qw2bd2lcw@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: (=?utf-8?Q?=22Rafa=C5=82_Mi=C5=82ecki=22's?= message of "Tue, 3 Jan 2017 21:20:49 +0100") Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: =?utf-8?Q?Rafa=C5=82_Mi=C5=82ecki?= Cc: Rob Herring , "linux-wireless@vger.kernel.org" , Martin Blumenstingl , Felix Fietkau , Arnd Bergmann , "devicetree@vger.kernel.org" , =?utf-8?Q?Rafa=C5=82_Mi=C5=82ecki?= List-Id: devicetree@vger.kernel.org Rafa=C5=82 Mi=C5=82ecki writes: > On 3 January 2017 at 20:55, Rob Herring wrote: >> On Wed, Dec 28, 2016 at 04:59:54PM +0100, Rafa=C5=82 Mi=C5=82ecki wrote: >>> From: Rafa=C5=82 Mi=C5=82ecki >>> >>> This new file should be used for properties handled at higher level and >>> so usable with all drivers. >> >> Why is this needed? Where would this data normally come from? > > Vendors limit choice of channels at their web user interface level. I > want to do better and report proper channels directly at kernel level > instead of masking them in every possible configuration tool. Why do vendors limit the channels? Is it because of a hardware limitation (antenna does not support, or not calibrated, for a certain band etc) or something else? --=20 Kalle Valo