[RFC 09/10] ath10k: htt: High latency TX support

Add HTT TX function for HL interfaces. Intended for SDIO and USB. Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/htt.h| 9 ++-- drivers/net/wireless/ath/ath10k/htt_tx.c | 72 +++- drivers/net/wireless/ath/ath10k/mac.c

[RFC 08/10] ath10k: add start_once support

Add possibility to configure the driver to only start target once. This can reduce startup time of SDIO devices significantly since loading the firmware can take a substantial amount of time. The patch is also necessary for high latency devices in general since it does not seem to be possible to

[RFC 04/10] ath10k: new fw fetch functionality

A new function for creating the fw file name dynamically. Since both SDIO and USB based chipsets will use different firmware from the PCIe and AHB chipsets, the fw file name is created dynamically. The new firmware names are: For PCIe and AHB: firmware-.bin (same as before) For SDIO:

[RFC 07/10] ath10k: per target configurablity of various items

Added ability to set bus type and configure the max number of peers in the ath10k_hw_params struct. With this functionality it is possible to have a different hw configuration depending on bus type for the same radio chipset. E.g. SDIO and USB devices using the same chipset as PCIe devices will

[RFC 06/10] ath10k: disable frame aggregation for high latency

This patch disables frame aggregation for HL interfaces. It is safest to do so until a mechanism for setting the limits from fw etc. has been implemented. Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/core.c | 9 +++--

[RFC 02/10] ath10k: usb support

usb HIF implementation Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/Kconfig |6 + drivers/net/wireless/ath/ath10k/Makefile |3 + drivers/net/wireless/ath/ath10k/usb.c| 1125 ++

[RFC 01/10] ath10k: various usb related definitions

Definitions for USB based chipsets Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/core.h | 3 +++ drivers/net/wireless/ath/ath10k/debug.h | 2 ++ 2 files changed, 5 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/core.h

[RFC v3 6/8] ath10k: sdio support

sdio/mailbox HIF implementation. Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/Kconfig |6 + drivers/net/wireless/ath/ath10k/Makefile |3 + drivers/net/wireless/ath/ath10k/sdio.c | 2105 ++

[RFC v3 3/8] ath10k: htc: move htc ctrl ep connect to htc_init

This patch moves the HTC ctrl service connect from htc_wait_target to htc_init. This is done in order to make sure the htc ctrl service is setup properly before hif_start is called. The reason for this is that we want the HTC ctrl service callback to be initialized before the target sends the

[RFC v3 7/8] ath10k: sdio get target info

Special BMI get target info function for SDIO. Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/bmi.c | 70 ++ drivers/net/wireless/ath/ath10k/bmi.h | 2 + drivers/net/wireless/ath/ath10k/core.c | 5 ++- 3 files

[RFC v3 4/8] ath10k: htc: refactorization

Code refactorization: Moved the code for ep 0 in ath10k_htc_rx_completion_handler to ath10k_htc_control_rx_complete. This eases the implementation of SDIO/mbox significantly since the ep_rx_complete cb is invoked directly from the SDIO/mbox hif layer. Since the ath10k_htc_control_rx_complete

[RFC v3 5/8] ath10k: various sdio related definitions

Debug masks for SDIO HIF layer. Address definitions for SDIO/mbox based chipsets. Augmented struct host_interest with more members. Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/core.h | 3 ++ drivers/net/wireless/ath/ath10k/debug.h | 2

[RFC v3 2/8] ath10k: htc: rx trailer lookahead support

The RX trailer parsing is now capable of parsing lookahead reports. A lookahead contains the first 4 bytes of the next HTC message (that will be read in the next SDIO read operation). Lookaheads are used by the SDIO/mbox HIF layer to determine if the next message is part of a bundle, which

[RFC v3 0/8] ath10k sdio support

This is the third version of the sdio RFC patch series. The actual sdio code (patch 6) has been subject to a massive overhaul, mainly as a result of Kalle's review comments. It no longer has any strong resemblance of the original ath6kl code from which it was originally based upon. Previous

[RFC v3 8/8] ath10k: htc: ready_ext msg support

Added support for extended ready message. The extended ready message contains the maximum bundle count supported by SDIO chipsets. It is transmitted by SDIO chipset only and replaces the "standard" ready message in this case. Signed-off-by: Erik Stromdahl ---

[RFC 03/10] ath10k: high_latency detection

The setup of high latency chips (USB and SDIO) is sometimes different than for chips using low latency interfaces. The bus type is used to determine if the interface is a high latency interface. Signed-off-by: Erik Stromdahl --- drivers/net/wireless/ath/ath10k/core.c

[RFC 00/10] ath10k usb support

This patch series adds usb support to ath10k. The target device used during development was a Linksys WUSB6100M based on QCA9377. I have tried to verify that the patches have not broken the existing PCIe support since some of the patches affect the generic code as well. To this end I have used a

[RFC 05/10] ath10k: htt: RX ring config HL support

Special HTT RX ring config message used by high latency devices. The main difference between HL and LL is that HL devices do not use shared memory between device and host and thus, no host paddr's are added to the RX config message. Signed-off-by: Erik Stromdahl ---

Re: [PATCH] ath10k: prevent sta pointer rcu violation

On 13 January 2017 at 08:24, Johannes Berg wrote: > >> Unless you then continue to use that sta pointer after you release >> data_lock. > > Ouch, ok. That's rather strangely hidden though. > >> Consider this: >> >> > CPU0 CPU1 >> > 1

[PATCH] ath10k: Search SMBIOS for OEM board file extension

Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different

[PATCH] ath10k: Fix per station tx bit rate reporting

From: Mohammed Shafi Shajakhan Not clearing the previous tx bit rate status results in a ambigous tx bit rate reporting to mac80211/cfg80211, for example the previous bit rate status would have been marked as legacy rate , while the current rate would have been an

Re: [1/2] ath10k: add accounting for the extended peer statistics

Christian Lamparter wrote: > The 10.4 firmware adds extended peer information to the > firmware's statistics payload. This additional info is > stored as a separate data field and the elements are > stored in their own "peers_extd" list. > > These elements can pile up in

Re: [v2,1/2] ath10k: refactor ath10k_peer_assoc_h_phymode()

Kalle Valo wrote: > When adding VHT160 support to ath10k_peer_assoc_h_phymode() the VHT mode > selection code becomes too complex. Simplify it by refactoring the vht part to > a separate function. > > Signed-off-by: Kalle Valo 2 patches applied

Re: ath10k: Fix Tx legacy rate reporting

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > Tx legacy rate is reported 10 fold, as below > > iw dev wlan#N station dump | grep "tx bitrate" > tx bitrate: 240.0 MBit/s > > This is because by mistake we

Re: ath10k: Fix wifi connectivity and warning in Rx with channel 169

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > In countries where basic operation of channel 169 is allowed, > this fixes the below WARN_ON_ONCE in Rx and fixes the station > connectivity failure in channel 169 as the