Re: [ath9k-devel] [RFC 0/3] of: add common bindings to (de)activate IEEE 802.11 bands

On Wed, Oct 5, 2016 at 1:36 PM, Felix Fietkau wrote: > On 2016-10-05 20:25, Martin Blumenstingl wrote: >> On Mon, Oct 3, 2016 at 5:22 PM, Rob Herring wrote: >>> On Sun, Oct 2, 2016 at 5:50 PM, Martin Blumenstingl >>> wrote:

Re: [ath9k-devel] [RFC 0/3] of: add common bindings to (de)activate IEEE 802.11 bands

On Wed, Oct 5, 2016 at 10:31 PM, Rob Herring wrote: > On Wed, Oct 5, 2016 at 1:36 PM, Felix Fietkau wrote: >> On 2016-10-05 20:25, Martin Blumenstingl wrote: >>> On Mon, Oct 3, 2016 at 5:22 PM, Rob Herring wrote: On Sun, Oct 2, 2016 at

Re: [ath9k-devel] [RFC 0/3] of: add common bindings to (de)activate IEEE 802.11 bands

On 2016-10-05 22:31, Rob Herring wrote: > On Wed, Oct 5, 2016 at 1:36 PM, Felix Fietkau wrote: >> On 2016-10-05 20:25, Martin Blumenstingl wrote: >>> On Mon, Oct 3, 2016 at 5:22 PM, Rob Herring wrote: On Sun, Oct 2, 2016 at 5:50 PM, Martin Blumenstingl

Re: [ath9k-devel] [RFC 0/3] of: add common bindings to (de)activate IEEE 802.11 bands

On 2016-10-05 20:25, Martin Blumenstingl wrote: > On Mon, Oct 3, 2016 at 5:22 PM, Rob Herring wrote: >> On Sun, Oct 2, 2016 at 5:50 PM, Martin Blumenstingl >> wrote: >>> There are at least two drivers (ath9k and mt76) out there, where >>>

Re: [ath9k-devel] [RFC 0/3] of: add common bindings to (de)activate IEEE 802.11 bands

On Mon, Oct 3, 2016 at 5:22 PM, Rob Herring wrote: > On Sun, Oct 2, 2016 at 5:50 PM, Martin Blumenstingl > wrote: >> There are at least two drivers (ath9k and mt76) out there, where >> devicetree authors need to override the enabled bands.

[ath9k-devel] [RFC 0/3] of: add common bindings to (de)activate IEEE 802.11 bands

There are at least two drivers (ath9k and mt76) out there, where devicetree authors need to override the enabled bands. For ath9k there is only one use-case: disabling a band which has been incorrectly enabled by the vendor in the EEPROM (enabling a band is not possible because the calibration