[ath9k-devel] [PATCH v6 0/3] add devicetree support to ath9k

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 as soon as the ath79 platform is ready to populate the ath9k wmac via devicetree. Changes since v5: - updated the example in the

[ath9k-devel] [PATCH v6 2/3] ath9k: add a helper to get the string representation of ath_bus_type

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(+)

[ath9k-devel] [PATCH v6 3/3] ath9k: parse the device configuration from an OF node

This allows configuring ath9k based PCI devices using devicetree. There is some out-of-tree code to "convert devicetree to ath9k_platform_data" (for example in OpenWrt and LEDE) which becomes obsolete with this patch. Signed-off-by: Martin Blumenstingl ---

[ath9k-devel] [PATCH v6 1/3] Documentation: dt: net: add ath9k wireless device binding

Add documentation how devicetree can be used to configure ath9k based devices. Signed-off-by: Martin Blumenstingl --- .../devicetree/bindings/net/wireless/qca,ath9k.txt | 39 ++ 1 file changed, 39 insertions(+) create mode 100644

Re: [ath9k-devel] ATH9K_HTC TX ENDPOINT

Hi, Am 06.09.2016 um 04:23 schrieb SangHyuk Kim: > Hi all, > > I wanna change registers at endpoint of TX using ATH9K_HTC driver. > > So I want to know where is the point that transmit a packet to air. > > Please anyone tell me. i'm not sure what you mean. But you probably wont to take a