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 devicetree. Changes since v7: - renamed node in the example (use wifi@... instead of ath9k@...), thanks Rob Herring for the hint - added the QCA PCI vendor ID and a list of PCI IDs with the corresponding chipsets. This documents all known PCI IDs, but some device IDs are used by multiple chipsets the list of chipset(s) per device ID may be incomplete. Also some chipsets seem to use multiple PCI device IDs, such as AR9485 as documented here: https://wiki.debian.org/ath9k Changes since v6: - updated documentation to reflect that "reg" is a mandatory attribute - dropped "qca,clk-25mhz" as it is only useful for AHB devices. OF support for AHB devices needs more work, so we can still introduce it later - removed qca,disable-2ghz and qca,disable-5ghz as these will be introduced as generic bindings in a separate series Changes since v5: - updated the example in the documentation (keeping it at a bare minimum: removed the PCI bridge, use a better real-world example with less-confusing device/fn numbers, added the actual size of the config space to the reg property) Martin Blumenstingl (3): Documentation: dt: net: add ath9k wireless device binding ath9k: add a helper to get the string representation of ath_bus_type ath9k: parse the device configuration from an OF node .../devicetree/bindings/net/wireless/qca,ath9k.txt | 48 ++++++++++++++++++++++ drivers/net/wireless/ath/ath.h | 6 +++ drivers/net/wireless/ath/ath9k/init.c | 42 +++++++++++++++++++ drivers/net/wireless/ath/main.c | 7 ++++ 4 files changed, 103 insertions(+) create mode 100644 Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt -- 2.10.0 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
