ping fails due to full_reorder_enable is not initialized in the
cdp_config. Fix the full_reorder_offload initializtion and enable
the full_reorder_enable by default.
Change-Id: I3191fb96a4d2fc365d5470c3144fdca5d3f59913
CRs-Fixed: 1098023
Relocate all the files under target folder to a new
fw-api repository. fw-api repository is created to automate
the interface interface change propagation. FW CLs will be
automatically propagated to the fw-api repository.
Change-Id: Ib5533cac57ae3364323b30d54d12b620a178f03a
CRs-Fixed: 1093452
The channel_list array for pcl channels is defined with size
QDF_MAX_NUM_CHAN. The index for the channel_list array can go
beyond QDF_MAX_NUM_CHAN.
The fix is to take care that the index for the channel list
for pcl channels does not exceed QDF_MAX_NUM_CHAN.
Change-Id: I1afd7e4b0ee13e02611cbc5f56a27d1da9ef06a6
CRs-Fixed: 1093129
Add API to call platform driver function in order to get SOC related
information for in PLD for PCIe.
Change-Id: Ieec098575b874e6d15ae45ef6000767ade7d459f
CRs-fixed: 1082183
These PLD APIs can be called to get PCIe MSI related information
from platform driver.
Change-Id: I2882f5c30d6f932c36af4503ac0bec9229ef35df
CRs-fixed: 1082183
In some cases, this TXRX_PRINT is taking more time to process as
some other printks' are already in progress. As this printk is
inside spinlock, so when some other core is also competiting for
this spinlock, that core keeps iterating in a loop. After some
time spinlock bug is triggered as it is suspected that this core
is locked on this spinlock.
This fix moves the TXRX_PRINT outside spinlock so that the other
core don't have to wait to acquire spinlock due to this printk.
Change-Id: Ie0fa7addd4f2a1272a4d5e287635b6a0f016ba97
CRs-Fixed: 1095406
Define basic dispatcher framework for init/deinit. Each individual
component is supposed to define its init/deinit primitives and replace
dummy place holder primitives.
Change-Id: I35140ea7af03ce568e1732435458caf78ab28996
CRs-Fixed: 1095741
prima to qcacld-3.0 propagation
This commit removes work-queue mechanism which is used to
trigger the TDLS Discovery request.
This eliminates concurrent TDLS data structures access.
Change-Id: Id6d6b38d2b17c4b1bab9b616b52e5a2d8c3475dc
Crs-Fixed: 798119
For unit-test suspend, pass a Host-to-Target Communication (HTC) Wakeup
flag to firmware with the WOW Enable command. This flag tells firmware
to always use the HTC wakeup method, even if GPIO (or any other) wakeup
method is available. This enables support for unit-test suspend on
emulation platforms with incomplete PCIe implementations, for example.
Change-Id: I82a70973b0d8845e05d6c82ab207ddef27447099
CRs-Fixed: 1093342
Log rx frag/tkip mic error packet in packetlog as per
rx frag indication message from firmware.
Change-Id: I4670c070e5affc5bf5b9f5ded23721e464a45737
CRs-Fixed: 1074043
qcacld-2.0 to qcacld-3.0 propagation
Firmware can't support all station feature and 32 ibss clients
in one bin because of the mem limitation. So host supports to
download IBSS firmware bin if con_mode=6.
CRs-Fixed: 962246
Change-Id: I6c3dca17c82fdfd2bdadcee319cc157e6aa2ead9
Update status code to QDF_STATUS_E_TIMEOUT before sending
ADD_BSS_RSP on ADD BSS timeout.
Change-Id: Ic5b393635c0aa9a6c80d2899eac3394de83d686a
CRs-Fixed: 1093188
Fix a race condition where the HTT peer map event is received before
the peer object is allocated in the data path.
CRs-Fixed: 1089662
Change-Id: I3931e6dbae3ec3a68d446c245432549fa635a97e
For Napier end-to-end bringup:
-- Disable PKTLOG, this is not ready on the new HW design
-- Enable timer based polling on DP UMAC rings
-- Modify cdp_soc_attach() to attach to Lithium DP
Change-Id: I096644887848dd8eae75bf4c497acc0b19f89833
CRs-Fixed: 1074199
Fix improper naming and exporting of dump_pkt() by:
1) adding ol_txrx prefix in the api
2) adding prototype of api to ol_txrx.h and removing the local
prototype for the api from core/dp/txrx/ol_tx_desc.c
CRs-Fixed: 1093667
Change-Id: I14e547223f8c96f10897aa6dc5c9781018a4d986
qcacld-2.0 to qcacld-3.0 propagation
Few logs for hdd_roam_tdls_status_update_handler()
is printing quite often and spamming the logs.
These logs are not for error.
Hence moving these logs to info log level.
Change-Id: Idbf423e34fad13fc787c6cdf9770cc9f15c923f9
CRs-Fixed: 1082364
qcacld-2.0 to qcacld-3.0 propagation
Add sanity check for tx desc to avoid crash if firmware report the invalid
msdu id to the host.
Change-Id: I5a339e81f3de882b5f7cc42b0628ea4738141c58
CRs-Fixed: 1071620
qcacld-2.0 to qcacld-3.0 propagation
TCP throttling logic changed a little after 3.19-rc1 kernel, which will
throttle the TCP packets to the host driver, it will heavily affect the
TCP UP Link throughput. So need to orphan the socket buffer asap, which
will call skb's destructor to notify the TCP stack that the SKB buffer is
unowned, And then the TCP stack will pump more packets to the host driver.
This kernel change's subject is "tcp: refine TSO autosizing".
And the commid id is: 605ad7f184b60cfaacbc038aa6c55ee68dee3c89
Here is the TCP TX throughput test data with 4.1 kernel on the customer TV,
the iperf's parameter is 85.3k, and 1 pair in default.
1. Without this change:
HT20: 35.1 Mbps
VHT80: 88.4 Mbps
88.4 Mbps (2 pairs)
2. With this change:
HT20: 82.3 Mbps
VHT80: 115 Mbps
164 Mbps (2 pairs)
And this change will enhance the UDP TX throughput too, but if more
packets from the kernel exceeding the driver's TX capability, the multiple
out of data packets will be dropped in the driver, so it needs to be
protected by TX following controlled (QCA_LL_TX_FLOW_CT).
And here is the UDP TX throughput data with 4.1 kernel on the customer TV:
1. Without this change:
HT20: 100 Mbps
VHT80: 155 Mbps
2. With this change
HT20: 124 Mbps
VHT80: 263 Mbps
Change-Id: I7f40c7b2c516d71f525fff4aaf2b8a71473b647f
CRs-Fixed: 1056126
QCA6290 is part of the Lithium chipset family. Without
support for lithium, compiling in the register deffinitions
for QCA6290 does not make sense.
Change-Id: Id251a931287d2662e0b910da299c12e9d45b719c
If WLAN FW crashes while in suspend mode then kernel tries to
resume the driver and WMA sends resume indication to WLAN FW and
waits for the response from WLAN FW. Since FW is already crashed,
there will not be any response from WLAN FW and wait logic waits
for the timeout before bailing out. This may cause delay in
completing the recovery and may cause other race conditions
becuase of that. To solve this, we registered for shutdown
notification so that call back would be called during recovery
and resume event can be set to make sure resume thread doesn't
just wait for the FW response. However, it takes around 7 ~ 12 secs
for platform driver to receive PD down notification and trigger
the recovery but wma only waits for 6 secs and still crashed
before recovery started. The fix it to extend WMA_RESUME_TIMEOUT
to 25 secs so that it can be interrupted gracefully by recovery
call backs.
CRs-Fixed: 1087911
Change-Id: Iba8b94111e4b4f0b0db8794e98c0645c667379a8
