Add documentation how devicetree can be used to configure ath9k based
devices.
Signed-off-by: Martin Blumenstingl
---
.../devicetree/bindings/net/wireless/qca,ath9k.txt | 48 ++
1 file changed, 48 insertions(+)
create mode 100644
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
This series adds support for configuring ath9k based devices via
devicetree. This was tested on PCI(e) based devices. This should work
for AHB based devices as well (adding more AHB specific properties may
still be needed) as soon as the ath79 platform is ready to populate the
ath9k wmac via
This can be used when the ath_bus_type has to be presented in a log
message or firmware filename.
Signed-off-by: Martin Blumenstingl
---
drivers/net/wireless/ath/ath.h | 6 ++
drivers/net/wireless/ath/main.c | 7 +++
2 files changed, 13 insertions(+)
This allows setting the MAC address and specifying that the firmware
will be requested from userspace (because there might not be a hardware
EEPROM connected to the chip) for ath9k based PCI devices using
the device tree.
There is some out-of-tree code to "convert devicetree to